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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the description's 'reads or computes only and changes nothing' mostly restates them. It does add genuinely non-schema behavior: automatic decoding when input already looks encoded, and per-call charging (first 25 free, failed calls free) which explains the idempotentHint=false cost implication. The lack of any statement about what the response looks like is the main remaining gap.

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 capability list and use case are front-loaded and every clause names a distinct format, so the long first sentence is dense rather than padded. The trailing pricing sentence is transactional necessity rather than description value, and the 'reads or computes only' clause is mild redundancy against the annotations.

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, no-output-schema tool this covers inputs, formats produced and billing well enough to call correctly. What is missing is how the result is shaped — whether all encodings are returned together or only those relevant to the input, and how the auto-decode path is signalled — which an agent would need to interpret the response.

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?

With 100% schema coverage the single 'text' parameter is already documented, including the 20,000-character limit, so the schema carries the load. The description nonetheless adds value by supplying a realistic sample value ('Café & <tags>') that shows the tool expects arbitrary mixed text rather than pre-encoded input.

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 concrete verb+resource ('every common encoding of one text in a single call') and enumerates the exact formats produced (Base64/Base64url, hex, URL component and full-URL, HTML, ROT13, code points, UTF-8 byte count, Punycode) plus automatic decoding. This clearly distinguishes it from the single-format siblings such as base64_encode, url_encode and text_caesar without opening any schema.

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?

'Use to prepare data for headers, URLs and markup, or to work out what an encoded string says' gives both a write-side and a read-side use case with a worked example (text=Café & <tags>). It does not explicitly say when to prefer this over the narrower base64_encode/url_encode siblings, so the boundary 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.