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

With readOnlyHint=true already declaring the safety profile, the description adds genuinely new behavioral context: the operation is fully offline and issues no network calls, so there is no latency, rate-limit, or side-effect risk. It also discloses that checksum validity is reported rather than enforced, implying invalid input is handled gracefully.

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?

A single dense sentence that front-loads the key constraint ('Offline') and then lists the outputs. Every clause earns its place; nothing is padding.

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?

No output schema exists, and the description compensates by stating what is returned (entity type, network, checksum validity), which is exactly what an agent needs. The lone parameter is fully documented, though error behavior for malformed non-bech32m input is not spelled out.

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?

One parameter with 100% schema description coverage ('Any Radix address or transaction id'), so the schema carries the semantics. The description slightly narrows scope to bech32m addresses, but adds no format, casing, or edge-case detail beyond the schema.

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?

Names a specific verb and resource ('Offline analysis of any Radix bech32m address') and enumerates what it extracts: entity type, network, checksum validity. The 'offline / no network calls' framing implicitly separates it from network-fetching siblings like lookup_entity, but it never names an alternative, so it stops short of full sibling differentiation.

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?

There is no explicit when-to-use/when-not guidance or named alternative among the many siblings (convert_olympia_address, resolve_vault_address, lookup_entity). The 'Offline... No network calls' phrase is only an implied selection cue — it tells the agent the tool is appropriate when a local, side-effect-free decode is wanted.

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