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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two non-obvious facts: the report is scoped to the caller, and a pass does not constitute approval without review. It omits behavior on an unknown/foreign id and what 'stored' implies about staleness.

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 short sentences with the purpose front-loaded and no filler. The caveat sentence earns its place conceptually, though its wording is dense and requires parsing.

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 should indicate what the 'check report' contains (per-check claims? statuses? timestamps?) and how it differs from the sibling review/artifact readers. Neither is covered, and the id parameter remains unexplained, so an agent cannot confidently call this 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 description coverage is 0%, so the description must carry the burden, and it does not: the single 'id' parameter is never explained (run id? artifact id? check id?), nor whether it must be owned by the caller. The only clue is the vague phrase 'the caller's stored check report'.

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+resource ('Read the caller's stored check report') is stated, but it is not reconciled with the tool name 'get_verification_run', leaving ambiguity about whether this returns a run status or a per-check report. Three closely related siblings (get_verification_review, get_verification_artifact, find_verification_checks) are never mentioned, so the agent must guess which one to pick.

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?

No statement of when to call this versus get_verification_review or get_verification_artifact, and no prerequisites (e.g. must a run exist, must the caller own it). The second sentence is about interpreting results, not about when to invoke the tool.

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