github_list_issue_comments

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

There are no annotations, so the description must disclose behavioral traits on its own. It only says 'List comments' and lists parameters. It does not mention that it is read-only, whether it supports pagination, how it handles max_results limits, what happens if the issue does not exist, or any authentication requirements. The description lacks meaningful behavioral context.

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?

The description is concise and well-structured. A single-line summary is followed by a clear parameter list. Every sentence is informative and there is no redundant text.

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 straightforward read-only list operation, the description is minimally sufficient. It omits usage guidance, behavioral details, and error handling, but the tool is simple and the output schema exists. Given the lack of annotations and the low schema coverage, more context would be beneficial, but it is not critically incomplete.

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?

Although schema description coverage is 0%, the description explicitly lists all five parameters with brief meanings (e.g., 'issue_number: Issue number', 'max_results: Maximum comments to return'). It adds value beyond the schema by explaining defaults and purpose, though it could be more detailed (e.g., expected formats, constraints).

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 description clearly states the tool's function: 'List comments on an issue.' This is a specific verb+resource pair, and it is distinguishable from sibling tools like create_issue_comment or get_issue. The purpose is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, alternatives, or specific contexts. The usage is only implied by the name and the action description, which is insufficient for an agent to decide when to select it.

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