vault_detokenize

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

Beyond annotations (readOnlyHint: true), description discloses failure behavior, rate limits (492/month, 50/sec), max values (4096), and case sensitivity. Adds substantial context about operational limits.

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?

Four sentences, each purposeful: main action, failure/alternative, rate limits, limits/case sensitivity. Front-loaded with primary purpose, no redundancy.

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?

Covers error conditions, scaling limits, case sensitivity, and alternative tool. With output schema present, return values are handled. All essential context for correct invocation is provided.

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 already provides description for 'tokens' parameter (dict mapping keys to tokens). Description adds token format (vaultd_XXXX...), max values, and case sensitivity, enhancing understanding beyond schema alone.

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?

States verb 'Detokenize', resource 'vault tokens', and outcome 'recover plaintext values'. Distinguishes from sibling vault_partial_detokenize by specifying it fails on non-valid tokens, indicating its purpose for pure token inputs.

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 about failure if any token is invalid and directs to vault_partial_detokenize for mixed inputs. Also provides rate limits and maximum batch size, giving clear constraints on usage.

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