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

Goes well past the readOnlyHint/openWorldHint annotations: it gives the exact return shapes for both modes, the non-UTF-8 hex fallback, and a pricing model (1 credit = 1 CAD cent per successful call) plus the billing rule that schema-invalid input is rejected before charging. Cost and validation behavior are not derivable from any structured field.

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?

Three dense sentences: action and scope first, return shapes second, cost/validation last. The middot-delimited return-shape notation packs two result structures into one line without waste.

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 no output schema, the description takes on the burden of describing returns and does so explicitly for both modes, including the null fields on decode. Cost and rejection-before-billing round out what an agent needs to call this confidently and cheaply.

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 coverage is 100%, so the parameter descriptions already carry the semantics and the baseline is 3. The prose restates variant as 'standard or url-safe' and mentions the hex decode path, but adds no format or constraint detail not already present in the schema — notably it never mentions the 48,000-character input cap.

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 — encodes UTF-8 text to standard or url-safe base64, or decodes either form — and adds the edge case that non-UTF-8 binary results are returned as hex. That detail separates it from siblings like hash or text-stats that also take text input.

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 two modes and their accepted input forms are spelled out clearly, so an agent knows what each call path does. It stops short of naming exclusions or a sibling alternative (e.g., when to reach for hash instead), so there is no explicit when-not guidance.

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