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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description usefully adds what the write actually is ('records a GAIP receipt only') plus cost/auth context ('Free, no account'). With no output schema, it also discloses the return shape (per-claim what GAIP saw, what you reported, whether they agree), which is the right burden to carry.

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?

Four tight sentences with the core action front-loaded, then inputs, then return shape, then constraints. No filler or restated name/title content.

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?

For an 11-parameter, nested-object tool with no output schema, the description covers the meaning of the main flow, the optional live-test path, and the return semantics. Secondary params (episode_id, task_class, continuity_handle, synthetic) are left to the schema, which documents them adequately, so completeness is solid though not exhaustive.

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%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the claim object's id requirement and the non-schema `check_url` field that triggers immediate GAIP testing, and clarifies that observations are your reported results versus GAIP's own findings. That earns above baseline.

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 ('check what an agent, API or supplier claims') and spells out the core mechanic (pass claims, optionally add check_url for GAIP to test live, supply observations). There are no siblings to distinguish from, and the scope is unambiguous.

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 when-to-use context ('Use this to check what an agent, API or supplier claims') plus a hard precondition ('Inputs must be public and non-personal'), and notes it is free with no account required. It stops short of explicit when-not-to-use guidance, but with no sibling tools the practical gap is small.

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