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

Annotations only indicate readOnlyHint=true, while the description adds behavioral traits: the response is deterministic, concise, grounded in a specific knowledge source, and free. This provides useful context beyond the annotations, though it does not detail failure modes or answer formatting. No contradiction exists.

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 terse sentence with no real filler. The leading 'FREE.' is arguably unnecessary, but it is short and harmless. Overall structure is acceptable for such a simple tool.

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 one-parameter, read-only Q&A tool, the description adequately states what the tool does, what input it needs, and what kind of output to expect. However, with no output schema and no discussion of out-of-scope questions or when to use a sibling tool, a few gaps remain.

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?

The schema has zero description coverage for the single 'query' parameter, so the description carries the semantic burden. It implies that query is the Bitcoin question being answered, which gives basic meaning, but it leaves the expected query format and ambiguous cases unaddressed. This earns a baseline 3.

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 clearly states the tool's action: returning a concise deterministic answer grounded only in California Bitcoin maintained knowledge. It identifies both the verb and resource, making the purpose fairly obvious, but it does not explicitly distinguish it from sibling tools like search_bitcoin_knowledge or verify_bitcoin_claim, so it stops short of a 5.

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 offers no guidance on when to choose this tool over its siblings, nor does it mention exclusions or alternatives. It simply describes the action without giving context about when a user request should be routed here versus search_bitcoin_knowledge, verify_bitcoin_claim, or deep_ground_bitcoin.

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