get_issue_comments

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no pagination behavior, no ordering, no volume expectations, and no indication of what is returned for an issue with no comments.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the second sentence duplicates the first almost exactly, so half the content is waste. Front-loading is fine, efficiency is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with annotations covering safety and no output schema, the main missing pieces are pagination/result-size expectations and clarification of the nested path parameter. Neither is addressed, leaving the agent to infer the invocation shape from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is a nested 'path' object wrapping issueId, which is an unusual shape an agent could easily get wrong. The phrase 'using its unique identifier' loosely points at issueId but never explains the path wrapper or the identifier's format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource ('Get all comments for an issue'), which is enough to separate it from write siblings like post_issue_comment and from the analogous get_test_case_comments / get_test_result_comments. The second sentence is a near-verbatim restatement that adds no distinguishing detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of the sibling alternatives (post_issue_comment, get_test_case_comments), and no prerequisites such as needing a valid issue ID. The only signal is the name itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.