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

The description adds meaningful context beyond the readOnlyHint annotation by disclosing the paid cost ('PAID $1.00 USD via Stripe MPP') and characterizing the output as 'deeper deterministic grounding.' This helps an agent understand the tool's cost and reproducibility, though it does not detail output format or rate limits.

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 concise with two short sentences and no filler. The payment disclosure is relevant for agent decision-making, though front-loading the functional purpose before the payment detail might improve scannability.

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, read-only tool, the description is somewhat sufficient: it states cost, general scope, and output type. However, it lacks details about what the grounding package will contain, how results are returned, and when a caller should prefer this over a sibling tool, leaving moderate ambiguity.

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 description does not explain the 'query' parameter beyond the parameter name itself. The domain and tool title suggest the query is a Bitcoin research topic, but the description provides no explicit semantics, format, or examples to compensate for the missing schema documentation.

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 action ('Produce a deeper deterministic grounding package') and identifies the resource scope ('canonical topics, claims, sources, and history'). It conveys more than the title's research label, though it does not explicitly differentiate itself from sibling tools such as get_bitcoin_evidence_pack or batch_bitcoin_research.

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 is provided on when to use this tool versus alternatives. The word 'deeper' implies a need for more thorough research, but there is no explicit when-to-use, when-not-to-use, or alternative routing among the seven sibling tools.

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