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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real context: the tickets:read permission requirement, the 1–50 limit and exclusive before_revision pagination semantics, and the important caveat that unavailable work is not proof of deletion or resolution. That caveat is behavioral insight found nowhere in the structured fields.

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 tight sentences with no padding, and the most decision-relevant content (what data is returned) is front-loaded. The phrasing is dense to the point of being slightly opaque, but every sentence contributes.

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 0% parameter coverage, the agent still lacks any description of what ticket_id is or the shape of the returned evidence/resolution payload. For a read tool with annotations, this is adequate but leaves noticeable gaps.

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%, so the description must carry the weight. It clarifies that before_revision is exclusive, which the schema does not state, but the limit range merely repeats the schema's min/max and ticket_id is left entirely unexplained.

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 verb 'Inspect' is generic, but the resource is unusually specific: original reviewed evidence, a separately labeled fresh assessment, and immutable owner resolution history. This clearly separates it from siblings like get_ticket_attention_review and list_reviewed_attention, though it never names those alternatives.

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?

'Current state always refers to the latest review' implies when the returned data is valid, but there is no explicit when-to-use vs. when-to-use-an-alternative guidance. No sibling is named and no exclusion is stated, leaving usage to inference.

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