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

Adds real context beyond the annotations: pure offline blocktools computation, nothing fetched or stored, and an explicit caveat that a listed chain is not a signing or recovery claim. That caveat usefully prevents over-reading the output; it stops short of describing the response shape.

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?

Front-loaded with the caveat and contents, then the one usage rule. The trailing swapchan_playbook sentence with seven workflow names is somewhat tangential and adds bulk, but even it earns partial place as routing guidance.

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?

A single optional parameter, no output schema, and the description still tells the agent what fields come back and the computational model. Missing only error behavior for bad tickers and explicit sibling disambiguation.

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 compensate — and it does, explaining the ticker format and the omit-for-all default behavior. It doesn't state what happens with an unrecognized ticker.

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 (chain parameter table) and enumerates its contents — Base58 version bytes, bech32 HRP, WIF byte, checksum, SLIP-44, tx format — plus the 80-chain scope. It does not, however, distinguish itself from the near-siblings get_supported_chains / supported_chains, which plausibly cover overlapping ground.

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?

Gives clear parameter usage ('chain=<ticker> for one, omit for all') and a hand-off to swapchan_playbook for workflows, but never says when to pick this over get_supported_chains/supported_chains. Usage is implied rather than stated.

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