skuuy_hash_encode

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

Annotations already declare readOnlyHint=true and idempotentHint=false. The description adds value by calling the utilities 'one-shot', noting cryptographically random password generation (which explains the non-idempotent flag), and providing a security caveat for MD5.

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 tight sentences with the operation list front-loaded and a single, earned parenthetical warning. No filler or repetition.

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 definition is largely complete for a simple utility tool: parameters are fully covered by schema and safety is covered by annotations. It does not specify the return format (e.g., hex digest for SHA-256, decoded string for base64_decode), which is a minor gap given no output schema exists.

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 schema already documents all parameters. The description only enumerates operations that match the enum and adds no extra syntax, format, or usage detail beyond what the schema provides.

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?

State a specific verb and resource: 'hashing/encoding utilities' with an enumerated list of operations. Siblings are network-oriented tools, so this is clearly distinct without needing to name an alternative.

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 warns that MD5 is for legacy checksum verification only and not for security, which is a clear when-not guidance. However, it does not explain when to choose SHA-256 vs SHA-512 or when to prefer base64 encode vs decode beyond the operation enum.

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