Base64 encode or decode

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is handled. The description adds the UTF-8 input assumption, which is genuinely useful, but says nothing about error behavior on malformed Base64 input or whether urlSafe is ignored when decoding.

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?

A single sentence that front-loads the action and covers both directions and both variants with zero filler. Nothing is redundant with the title or schema.

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 three-parameter, stateless, non-destructive utility with no output schema, the description covers enough to invoke it correctly. The remaining gap is mode-dependent parameter behavior (urlSafe on decode) rather than anything structural.

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 0%, so the description must carry parameter meaning. It does cover the core semantics of text, mode, and the standard/URL-safe distinction, but it omits that urlSafe defaults to false and, more importantly, that it has no effect in decode mode, which is the most likely source of a wrong call.

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 reversible transform with both directions ('Encode UTF-8 text to Base64 ... or decode Base64 back to text') and names the two encoding variants. It does not explicitly draw the boundary against the nearest sibling, hash_text, which also transforms text input, but no sibling performs Base64 so confusion risk is low.

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?

Usage is only implied by the mode enum ('encode or decode'). The description gives no guidance on when to prefer standard vs URL-safe output, and no note on which mode consumes which input form. An agent must infer everything from the parameter names.

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