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

No annotations are provided, so the description carries the full behavioral burden. It discloses the per-call cost ($0.05 USDC on Base) and the evidence-coverage profile ('balanced'), which are useful. But it omits payment mechanics, return behavior, read-only status, rate limits, and error handling for an 11-parameter tool.

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, front-loading the tier/coverage then the cost. No filler; every sentence carries information. Structure is clean even if content is sparse.

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?

Given 11 parameters, one required, no output schema, and no annotations, this description is far too thin. It gives cost and a vague coverage label but leaves parameter behavior, usage, and return semantics entirely unspecified.

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 only 18% (claim and asOf only), so the description must compensate for nine undocumented parameters. It adds no parameter meaning, no defaults, no explanation of sourcePolicy, maxSources, freshnessHours, etc. This is the key gap.

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 resource (claim verification) and a tier qualifier ('Standard') with 'balanced evidence coverage,' which implicitly distinguishes it from quick/deep/research siblings. However, it never names the siblings or spells out what 'balanced' means, so differentiation is implicit rather than explicit.

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 guidance on when to use this tier versus verify_claim_quick, verify_claim_deep, verify_claim_research, or list_verification_tiers. The word 'Standard' hints at a default tier but the description gives no conditions, prerequisites, or alternatives.

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