crypto_decode

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

Describes the decoding action and auto-detection behavior. No annotations provided, but description does not disclose any side effects, auth needs, or limitations. Adequate but not detailed.

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?

Two concise sentences front-loading all supported formats and the auto mode feature. No redundant information.

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?

Provides core functionality but omits output format and error handling. Without output schema, agent lacks info on return value. Sufficient for simple usage but not fully 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?

Schema covers both parameters with descriptions. Description adds value by explaining auto mode behavior for encoding parameter, beyond enum list. Does not elaborate on input format specifics.

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?

Clearly specifies it is a multi-format decoder supporting Base64, hex, binary, etc. Distinct from sibling tools like crypto_detect or crypto_entropy, which are not decoders.

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?

States it is a decoder for multiple formats and mentions auto mode, implying use when decoding various encodings. Lacks explicit when-not or alternatives, but sibling context shows it is the only decoder.

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