base64_encode

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

No annotations are provided, so the description fully carries the burden. It explicitly states 'Pure local encoding with no network calls' and 'Always succeeds for valid UTF-8 input', covering safety and reliability. The encoding alphabet and return format are also specified, leaving no ambiguity about behavior.

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, coherent paragraph that front-loads the core action, then provides usage guidance and behavioral details. Every sentence contributes value, but it could be slightly tighter by combining the usage and warning sentences.

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?

The description covers return value and success condition, but lacks mention of error handling for non-UTF-8 input. Given no output schema and the simplicity of the tool, this is a minor gap. Overall, it is fairly complete.

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 input schema already has 100% coverage with a clear description of the required 'input' parameter. The description adds little beyond restating that it is a UTF-8 string, which is already in the schema. Therefore, a baseline score of 3 is appropriate.

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 clearly states the action ('encode a UTF-8 plaintext string'), the resource ('string'), and specifies the standard (RFC 4648 §4, +/= alphabet). It also distinguishes from sibling tools like url_encode and base64_decode by focusing on Base64 encoding, and even contrasts with URL-safe Base64.

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 explicit use cases: 'use when you need to embed binary-safe text in HTTP headers, data URIs, or JSON payloads'. It also includes a note about when this tool is not suitable (if URL-safe Base64 needed), but does not name a specific sibling tool for that purpose, so it misses the highest score.

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