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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint, so the description only needs to add behavioral nuance. It adds the comment-coverage distinction versus list_issue_attachments, but it does not describe return format or whether results are limited to direct attachments, so the added transparency is moderate.

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?

Three sentences carry the purpose, the routing alternative, and the intended scope with virtually no filler. It is slightly less crisp than ideal because the first and third sentences overlap in scope, but each sentence contributes 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 simple read-only list with two fully documented parameters and strong annotations, the description covers the main selection decision. It does not specify return shape, but with no output schema and a straightforward list resource this is an acceptable gap rather than a blocking omission.

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?

Input schema fully documents both parameters (100% coverage), so the baseline is 3 and the description does not need to restate them. The description does not add parameter-level details, and the schema's parentId note ('Issue identifiers are not accepted') is left unresolved by 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?

Description states a clear action and resource: it lists files attached to an issue, comment, doc, or project, and names the sibling tool that should be used for issues. It stops short of 5 because the final sentence, 'This is for docs and projects,' slightly muddles the scope after the first sentence explicitly included comments and issues.

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?

It explicitly tells the agent to use list_issue_attachments for an issue because that tool also covers issue comments. This is strong routing guidance, but it does not fully explain when to choose this tool for comments, and the final sentence only loosely states the intended use case.

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