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

Annotations only indicate readOnlyHint=true, so the description adds value by disclosing a payment/cost element ('PAID $0.50 USD via Stripe MPP') and the verification behavior against canonical statements. It does not contradict the annotations and provides useful behavioral context beyond them.

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 brief and mostly front-loaded, stating the cost first and then the core action. The payment sentence is unusual but earns its place as behavioral context, and the rest is tight 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?

For a single-parameter tool with no output schema, the description adequately covers input, action, and the shape of results ('supported, unsupported, or uncertain evidence'). It does not explain what 'canonical maintained statements' consist of, but that is not essential for calling the tool 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%, and the only parameter is 'claim'. The description compensates by explicitly using and defining the claim as the object of verification, giving the parameter practical meaning beyond the bare schema name.

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 states a specific verb ('Verify'), a clear resource ('a claim against canonical maintained statements'), and the three possible outcomes ('supported, unsupported, or uncertain evidence'). This distinguishes it from sibling tools like answer_bitcoin_question or search_bitcoin_knowledge, which target different actions.

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 description makes clear that this tool is for verification of claims rather than open-ended answering or research. It does not explicitly name alternatives or exclusion conditions, but the purpose is specific enough for an agent to infer when to select it.

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