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

No annotations exist, so the description carries the full disclosure burden and meets it thoroughly. It reveals ordering behavior (newest first), pagination limits (50 per page, hasNextPage), entry composition (when, who, API key attribution, what operation, readable change lines), and a truncation behavior ('Long content is shortened').

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 definition is information-dense with no filler: every clause contributes (scope, ordering, pagination, entry fields, examples, truncation). It is a single long sentence that could be split for readability, but nothing is wasted.

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?

With no output schema and no annotations, the description must carry the full burden of explaining the return shape, and it does: entry fields, field semantics, representative change-line examples, and truncation behavior are all specified. An agent has everything needed to call and interpret results correctly.

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 coverage is 100%, so the baseline of 3 applies. The page and count descriptions in the schema already explain their semantics well; the tool description adds context about the 50-per-page default and hasNextPage linkage, but does not materially extend what the schema already states.

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 gives a specific verb-resource pair ('Lists an issue's change history') and clarifies scope ('the issue and its comments'), which distinguishes it from siblings like get_issue (current state) and list_issue_comments (comments only). The ordering and pagination details further pin down exactly what this tool returns.

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 concrete operating instructions: newest-first ordering, a 50-entry page cap, and how to detect more pages via hasNextPage. It does not explicitly name sibling alternatives or state when not to use this tool, but the pagination and filtering context is clear enough for an agent to invoke it correctly.

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