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

Beyond the ambiguous idempotentHint, the description does not disclose key derivation details, IV/nonce behavior, output format (e.g., base64, hex, tags), or reversibility. This is a significant gap for an encryption tool that must be correctly invoked.

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 concise sentence with no irrelevant content. It is front-loaded and to the point.

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?

No output schema exists, and the description does not explain what the encrypted result looks like or any security context. Given the simplicity of the tool, it should at least mention the output format or passphrase handling.

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% with clear parameter descriptions, so the baseline is 3. The description itself adds no further semantic detail beyond what the schema already 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?

The description clearly states the tool encrypts text using a specific algorithm (AES-256-GCM) with a passphrase. The verb 'encrypt' and resource 'text' are explicit, and it distinguishes from siblings like security_decrypt and dev_hash.

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?

Usage is implied by the name and description, but there is no explicit guidance on when to use this tool versus alternatives such as hashing, signing, or decryption. No exclusions or alternative tool references are provided.

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