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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool operates offline, supports both encode and decode, and expects inputs prefixed with 'hex:' or 'b58:'. This goes well beyond a bare 'encode/decode' statement and gives the agent a reliable mental model of how the tool behaves.

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, dense sentence that front-loads the purpose, includes the critical input format, and notes the offline capability. Every word adds value; there is no repetition of the title or schema and no extraneous detail. This is excellent concise writing.

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 simple one-parameter codec, the description is nearly complete. It explains purpose, input format, and offline nature. An output schema exists to describe return values, and the behavior with prefixes is sufficient for correct invocation. The only minor gap is the lack of explicit error-handling information, but that is not essential for a straightforward codec 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?

The parameter 'q' has no schema description (0% coverage), but the tool description compensates by explaining the expected input format: 'hex:..' / 'b58:..'. This adds meaning beyond the bare property name and default empty string, telling the agent exactly how to format values for q. It doesn't cover behavior with empty input, but the core semantics are well defined.

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 verb and resource: 'Base58 Codec: Bitcoin base58 encode/decode'. It also gives concrete input formats ('hex:..' / 'b58:..'), which clearly differentiates it from sibling codec tools like base64, base32, and ascii85. An agent can immediately tell this is for Bitcoin base58 conversion without inspecting other tools.

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 provides clear context: it is for Bitcoin base58 encoding/decoding and works offline. While it doesn't explicitly name alternatives or when-not-to-use conditions, the Bitcoin-specific framing and the format hints make the intended use case obvious. This qualifies as clear context with no exclusions.

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