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

Annotations already cover readOnly, destructive, and idempotent hints, so the bar is lower. The description adds genuinely non-redundant context: missing padding is tolerated, pricing model (first 25 free, $0.01/call, failed calls free), and reinforces non-idempotent cost behavior ('repeats are not free').

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?

Front-loaded with the operation, then tolerance, then use cases, then pricing. The pricing sentence is longer than strictly needed but is behaviorally relevant to the calling agent; nothing is wasted on restating the name.

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 single-parameter utility with no output schema, the description covers input forms (standard/URL-safe, padding tolerant), usage context, and cost behavior. Only the failure mode (what happens on invalid base64) is left implicit.

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% and the single parameter is described as 'The base64 text'. The description goes beyond the schema by noting padding tolerance and giving a concrete invocation example (text=aGVsbG8gd29ybGQ=), which clarifies accepted input forms.

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+resource: 'Decode standard or URL-safe base64 to UTF-8 text', including both variants handled. The sibling base64_encode is implicitly the inverse, and the title/description make the direction of the operation unambiguous.

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 read encoded headers, tokens and data URLs' gives concrete use cases, which distinguishes it from base64_encode and hints at where the input comes from. No explicit when-not or named alternative, but the direction (decode vs encode) is clear from the definition.

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