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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description is free to add value elsewhere, and it does by detailing the returned contents—aggregate counts, first/last release, latest event frames, last 20 breadcrumbs, common tag values, and comments. It omits behavior like not-found handling or event pagination, but with no output schema this payload disclosure is genuinely useful context beyond the annotations.

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 scope statement is correctly front-loaded, but everything else is compressed into one very long comma-separated sentence. Every listed item is potentially useful, yet the lack of sub-structure makes the payload list hard to scan.

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, the description carries the return-value burden and does so comprehensively, and the annotations handle safety. Gaps remain around missing-issue behavior and how nested collections (breadcrumbs, tags, comments) are bounded, so it is strong but not fully complete.

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 schema fully documents issueId, appId, range, and environment, and the baseline is 3. The phrase 'counts for the environment and range' gestures at two of those params but adds no semantics beyond 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?

Opening with 'One issue:' paired with the get_issue name makes the singular-retrieval scope clear and distinguishes it from list_issues and list_issue_events among the siblings. The remainder enumerates the payload fields rather than restating purpose, so the tool's job lands but is never stated as an explicit verb+resource.

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?

There is no when-to-use guidance, no prerequisites (e.g. that appId is required to scope the call), and no reference to alternatives such as list_issues or search_events. The only usage-adjacent detail, '14d when left out', lives in the schema, not the description.

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