list_issue_comments

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds value by warning that comment bodies and author names are untrusted repository data — a useful security cue. However, it doesn't disclose the bounded page behavior details beyond what's in the schema, nor does it note any rate-limit or auth requirements that would enrich the annotation baseline.

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?

Two concise sentences with zero wasted words. The description front-loads the core purpose and adds the untrusted-data warning efficiently. Well-structured and appropriately brief.

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 read-only pagination tool with good annotations, the description adequately covers purpose and safety. However, given 6 parameters and only 17% schema coverage, the description could do more to explain the required account/repository/issueNumber relationship and pagination semantics. No output schema exists, so some return-format expectations are left to the agent's inference.

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 only 17%, so the description must compensate for undocumented parameters. The description mentions 'one bounded page' which hints at page/perPage semantics, but doesn't explain the parameters in detail. The repository field has inline schema documentation, but account, hostname, issueNumber, page, and perPage semantics beyond field types are not elaborated in the description.

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 it reads one bounded page of issue comments from an allowed repository — a specific verb + resource with paging scope. It distinguishes itself from siblings like list_issue_events and comment_issue by focusing on reading comments specifically, though it doesn't explicitly name alternative tools.

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?

No explicit when-to-use guidance or exclusions provided. It doesn't mention pagination strategy guidance (e.g., use page to navigate, perPage bounds) even though these are relevant for a paged read tool, nor does it clarify how this differs from list_issue_events or list_pull_request_review_comments.

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