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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds real behavioral detail beyond them: it discloses that comments are inlined and that attachments are returned as metadata only, not content, which prevents an agent from expecting file bodies. No mention of permissions or pagination limits keeps this from a 5.

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, front-loaded with the returned-content list and the routing hint at the end. Efficient overall, though the parenthetical about comments is slightly long and could be tightened without losing meaning.

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 burden and does it: it enumerates the fields returned and explicitly scopes attachments to metadata. An agent knows what it will receive and where to go next, so nothing material is missing.

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 0% for the single issueId parameter, and the description never clarifies its expected format (e.g., 'ISS-123') or whether it accepts a key vs. numeric id. The name is largely self-descriptive, so this is adequate but leaves the gap the description should have filled.

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+resource ('Full detail on one Issue') and then enumerates exactly which fields come back (status, severity, owner/reporter, resolution, linked Task/Risk/CR, recent comments, attachment metadata). This lets an agent separate it from list_issues (many), get_issue_history (history only), and list_comments (comments only) without opening any schema.

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?

Gives clear context ('triage starts here' on a bug report) and names the follow-up alternative explicitly ('use read_issue_attachment to open one'), plus the avoidance case for list_comments. No explicit when-not condition or comparison against the sibling list_issues, so it falls just short of a 5.

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