base64_convert

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

No annotations are provided, so the description carries full burden. It only states the core operation, but fails to disclose important behavioral traits such as error handling for invalid Base64 input, handling of whitespace, or output formatting. This leaves the agent without guidance on edge cases.

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, front-loaded sentence that directly states the tool's purpose. Every word earns its place with no filler or repetition. It is concise and well-structured.

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 tool is simple, but the description omits critical information about how to select the encoding vs decoding mode via the 'mode' parameter. It also lacks details on validation or error behavior. The presence of an output schema reduces the need to explain return values, but the missing mode semantics and edge-case behavior make it minimally adequate.

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 schema has two parameters ('mode' with default 'encode' and 'text') but no descriptions, and the tool description does not explain how these parameters map to the operations. The phrase 'Encode a UTF-8 string' implies 'text' is the input, but 'mode' is never mentioned, making its role ambiguous. With 0% schema coverage, description fails to compensate.

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 both operations: encoding a UTF-8 string to Base64 and decoding Base64 back to text. It uses specific verbs ('Encode', 'decode') and specifies the resource (Base64), making it distinct from sibling tools like generate_uuid or format_json.

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 context is clear: use this tool when you need Base64 conversion. It implicitly covers both directions (encode/decode) but does not explicitly mention when to choose one over the other (which depends on the 'mode' parameter). There are no alternative tools named, but for a simple conversion utility this is sufficient.

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