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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so restating 'read-only, no network' is largely redundant. What genuinely adds value is the operational limit set — 64 KB JSON input, 1 s per call, 1 MB result — which no annotation or schema field conveys and which an agent needs to avoid failed calls.

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 labelled structure (When / Not for / Side effects / Deterministic / Limits) is well front-loaded and easy to scan. But the entire block is duplicated in Spanish and English, roughly doubling length with zero informational gain for the calling agent, which dilutes the useful content.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values; it still covers purpose, routing, limits and determinism. The only residual gap is the contradictory 'to or from this encoding' phrasing on an encode-only tool.

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 100% and all three parameters (hrp, variant, data_hex) are fully documented with patterns, bounds, enum and default in the schema itself. The description adds only the conceptual framing of hrp as a 'human-readable prefix' and the byte-width conversion, so the baseline 3 applies.

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 verb and resource (encode hex bytes plus a human-readable part) into Bech32/Bech32m, names both BIP-173 and BIP-350, and even describes the transformation (8-bit bytes to 5-bit groups). It is unambiguously distinguishable from bech32-decode and from the many other base32/base58/base64 encoders in the sibling list.

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?

Explicit 'When:' and 'Not for: decoding ... (bech32-decode)' clauses route the agent correctly and name the alternative sibling. However, the 'When' clause also says 'to or from this encoding' ('o desde ella'), which blurs the very boundary the 'Not for' sentence draws, since decoding is exactly what it says not to use this tool for.

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