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

With no annotations provided, the description carries the full burden, and it delivers: pagination behavior, ordering, canManage semantics for mutation tools, comment fields, and attachment id usage with get_attachment. This gives an agent enough behavioral context to call and interpret the result correctly.

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 sentences, no filler, with the core listing behavior front-loaded and the valuable field/permission detail following directly. Every clause adds useful information.

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 list tool with no output schema and no annotations, this description is unusually complete: it explains pagination, result ordering, returned fields, permission implications, and how attachment ids relate to another tool. An agent has what it needs to invoke the tool and use the response.

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 100%, so the schema already documents the three parameters clearly. The description adds general context about pagination and defaults but doesn't materially improve on the parameter-level documentation provided in the schema.

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?

States a specific verb ('Lists'), the resource ('an issue's comments'), and key behavioral details ('oldest first', 'up to 50 per page'). This clearly distinguishes it from sibling tools like create_comment, edit_comment, and delete_comment, which have different purposes.

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 makes the tool's use context clear: retrieve an issue's comments with pagination, and use canManage to decide whether edit_comment/delete_comment is permitted. It doesn't explicitly state when not to use it, but the purpose is unmistakable relative to the sibling list.

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