user25568: To cite hyperlinks in comment; I use the command format: 
Here's an inline link to [Google](http://www.google.com/).,
out of from total 3 formats. 
I've experienced, if the link-address being cited, itself contains a pair of first bracket, it gives rise to a strange situation. 
screenshot-1
 
( comment permalink )

( comment permalink ) 
So, my question is;  Is there any way to code them properly?

P.S.

The bug not affecting the answering. It is only affecting the commenting.
I do not use later-2 commands for commenting because... 
I've tested the other 2 formats in commenting; but that doesn't work. such as :

Here's a reference-style link to [Google][1].  [1]: http://www.google.com/ gives rise to 
screenshot  - 3

( comment example permalink)
and 
Here's a very readable link to [Yahoo!][yahoo].  [yahoo]: http://www.yahoo.com/
screenshot-4

( comment example permalink) ;
So seemingly the later-2 format not for use in comments.

user-1: The parentheses in URL are not a problem: for example,
[text](https://en.wikipedia.org/wiki/Barbel_(anatomy)) works fine in comments without any escaping. It doesn't work in yours because you typed something with a whitespace within the URL parentheses: 
[text](https://en.wikipedia.org/wiki/Barbel_(anatomy) something)

which of course broke the syntax.

The inline style text is the only option for comments. When a character contained in the URL gets misinterpreted, escape it with a backslash \: for example, \[ instead of [. But this doesn't seem to be necessary for parentheses and brackets.

25568: <p>To cite hyperlinks in comment; I use the command format: </p>

<p><code>Here's an inline link to [Google](http://www.google.com/).</code>,<br>
out of <a href="https://biology.stackexchange.com/help/formatting">from total 3 formats</a>. </p>

<p>I've experienced, if the link-address being cited, itself contains a pair of first bracket, it gives rise to a strange situation. </p>

<p>screenshot-1</p>

<p><a href="https://i.stack.imgur.com/s8ESY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/s8ESY.png" alt="bug example-1"></a> </p>

<p>( <a href="https://biology.stackexchange.com/questions/7932/why-are-there-no-wheeled-animals/30947#comment96120_30947">comment permalink</a> )</p>

<p><a href="https://i.stack.imgur.com/jUjIL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/jUjIL.png" alt="bug example 2"></a></p>

<p>( <a href="https://biology.stackexchange.com/questions/54332/which-fish-is-this#comment95742_54332">comment permalink</a> ) </p>

<p>So, my question is;  <em>Is there any way to code them properly?</em></p>

<hr>

<h2>P.S.</h2>

<ol>
<li><p>The bug not affecting the answering. It is only affecting the commenting.</p></li>
<li><p>I do not use later-2 commands for commenting because... </p>

<p>I've tested the other 2 formats in commenting; but that doesn't work. such as :</p></li>
</ol>

<p><code>Here's a reference-style link to [Google][1].  [1]: http://www.google.com/</code> gives rise to </p>

<p>screenshot  - 3
<a href="https://i.stack.imgur.com/GFRfs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/GFRfs.png" alt="sandboxed"></a><br>
( <a href="https://biology.meta.stackexchange.com/questions/654/stack-exchange-experimentation-sandbox/3480#3480">comment example permalink</a>)</p>

<p>and </p>

<p><code>Here's a very readable link to [Yahoo!][yahoo].  [yahoo]: http://www.yahoo.com/</code></p>

<p>screenshot-4
<a href="https://i.stack.imgur.com/ZLERR.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZLERR.png" alt="enter image description here"></a><br>
( <a href="https://biology.meta.stackexchange.com/questions/654/stack-exchange-experimentation-sandbox/3480#comment4341_3480">comment example permalink</a>) ;</p>

<p>So seemingly the later-2 format not for use in comments.</p>
 -1: <p>The parentheses in URL are not a problem: for example,<br>
<code>[text](https://en.wikipedia.org/wiki/Barbel_(anatomy))</code> works fine in comments without any escaping. It doesn't work in yours because you typed something with a whitespace within the URL parentheses: </p>

<pre><code>[text](https://en.wikipedia.org/wiki/Barbel_(anatomy) something)
</code></pre>

<p>which of course broke the syntax.</p>

<hr>

<p>The inline style text is the only option for comments. When a character contained in the URL gets misinterpreted, escape it with a backslash <code>\</code>: for example, <code>\[</code> instead of <code>[</code>. But this doesn't seem to be necessary for parentheses and brackets.</p>
