base64

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

The description states 'Read-only, no side effects' and explains output format: 'Returns JSON with the result by default; use --raw for raw output on stdout.' Annotations already provided readOnlyHint, so the description adds value by clarifying output modes. However, it does not detail the behavior of encoding parameters or error handling, which are covered only in the schema.

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 concise (4 sentences) and front-loaded with the core purpose. Every sentence adds value: purpose, output mode, usage context, and alternatives. No wasted words.

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?

Given the high parameter count (8) and no output schema, the description adequately covers the primary function, output format, and alternative tools. However, it could be more complete by briefly describing the JSON result structure or common encoding scenarios. Still, it is sufficient for most use cases.

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 100%, so the baseline is 3. The description adds minimal parameter details beyond the schema (only mentions --raw and default output). It does not elaborate on encoding parameters or other options.

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 explicitly states 'Encode or decode base64 data from files or stdin', providing a clear verb and resource. It distinguishes from siblings by mentioning 'basenc' and 'base32' as alternatives for other base encodings.

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 guidance: 'Use for standard base64 encoding in data transfer and storage. Not for flexible multi-base handling — use 'basenc'... See also 'base32', 'basenc'.' This clearly states when to use this tool and recommends alternatives.

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