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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of the return payload (evidence types and remediation profile sections) in the absence of an output schema, though it says nothing about size, pagination, or whether all evidence is always present.

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?

A single dense sentence with the parenthetical example list doing useful specification work rather than padding. It is front-loaded with the core object ('One issue with the evidence...'), though it opens as a noun fragment rather than a complete directive statement.

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 of describing returns and does so at a useful level of detail for a simple two-parameter read tool. The only gap is failing to clarify the overlap with get_remediation_profile, which could cause a redundant or wrong tool choice.

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% and both parameters (issue_id, project_id) are documented in-schema, including the pointer to list_issues. The description adds no parameter syntax or scoping detail beyond the schema, so the baseline 3 applies.

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 specifies the resource (a single issue) and enumerates the payload: scanner evidence (offending tag, heading outline, redirect chain, JSON-LD block) plus the remediation profile. It is clearly distinct from list_issues in being singular, and from get_remediation_profile in bundling remediation with the issue, though it never explicitly names either sibling or uses a verb like 'retrieve'.

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 statement of when to call this versus list_issues (to find an id) or get_remediation_profile (which appears to return overlapping remediation content). No prerequisites, no exclusions — the agent must infer usage from the name alone.

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