basenc

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

Annotations already declare readOnlyHint=true; description reinforces with 'Read-only, no side effects' and adds behavioral details like default JSON output, raw bytes option, and bounding output size with max_output_bytes. No contradictions.

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?

Highly concise: two sentences cover purpose, options, and usage guidance. Front-loaded with core functionality, then flags. 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?

Adequately covers all key aspects: input sources, format selection, output modes, safety. No output schema but description explains return format. Could mention example or return structure, but sufficient given 6 params and no output schema.

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 description adds meaning beyond schema: explains default base, decode mode, raw output, max_output_bytes significance, and default input source. Adds value but some params (encoding) are less explained; still above baseline.

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?

Description clearly states verb 'encode/decode' and specific resources 'data in base16, base32, base64, base64url' from files/stdin. It distinguishes from sibling tools by noting flexible base selection vs fixed-format needs.

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?

Explicitly states when to use ('flexible base selection'), when not ('fixed-format needs'), and provides alternatives ('use base64 or base32 for dedicated encoding'). Also covers when to use --raw and --max_output_bytes.

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