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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context: it does not spend a verification (a cost-related detail) and operates 'on this account.' This goes beyond the annotation hints, indicating a read-only, account-scoped lookup. No contradictions with annotations.

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?

The description is a single, concise sentence (14 words) that immediately states the purpose and key differentiator ('without spending a verification'). No filler or repetition; every word earns its place.

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 a simple read-only lookup tool with one string parameter and no output schema, the description covers the essential context: what it checks, scope (this account), and cost implications. It does not specify the return format, but 'whether' strongly implies a boolean outcome, which is sufficient for this complexity level.

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 clarify the parameter. The description implies 'claim' is a previously submitted statement whose verification state is being checked, which adds some meaning beyond the plain string name. However, it does not specify format, exactness, or any normalization requirements, leaving room for ambiguity.

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 description uses a specific verb ('look up') and clearly identifies the resource ('whether a claim has already been verified on this account'). It distinguishes itself from sibling tools by explicitly noting it does not spend a verification, contrasting with verify_claims.

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?

The phrase 'without spending a verification' implies a clear use case: check prior verification status when you want to avoid the cost of verifying. This provides clear context for when to use the tool, though it does not explicitly name alternatives or provide exclusionary guidance.

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