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

Goes well beyond the read-only/non-destructive annotations: it discloses that each page is fetched exactly once, that robots.txt is respected, the exact result vocabulary including SOURCE_UNREACHABLE, and that a receipt and excerpt are returned. It also states cost/auth ('free, read-only, no account') and an input restriction (public, non-personal).

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 dense sentences: trigger condition first, then the parameter shape, then behavior and return vocabulary. Every clause carries information (batching limit, fetch semantics, result codes, cost, input restriction) with no filler.

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 return-value burden and does so by naming the status codes, excerpt, and receipt. Combined with fully described parameters and annotation-provided safety profile, an agent has everything needed to call this correctly on the first try.

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 coverage is 100%, so url/quote/claimed_title/claimed_date and the data_classification enum are already documented structurally, which sets the baseline at 3. The description usefully restates the 1-20 bound and the public/non-personal restriction, but adds no per-field syntax or format detail beyond the schema.

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 ('verify citations or quotes') with a quoted user phrasing that maps directly to the task, and the returned status vocabulary (QUOTE_FOUND etc.) makes the output contract unambiguous. Clearly distinct from siblings like gaip_watch_register or witness_dispute_bundle, which handle different lifecycle stages.

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?

'Use this when asked to verify citations or quotes ("do these sources really say this?")' gives a clear triggering condition, and the 1-20 citation constraint implies the batch scope. No explicit when-not or alternative-tool routing (e.g., vs. verify_gaip_receipt), so it stops 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.