secret_reveal

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

No annotations are provided, so the description must cover behavior. It discloses that the tool will fail due to server configuration and that it returns plaintext, but it does not describe behavior when the tool succeeds or other operational details.

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 paragraph that front-loads the critical failure information. It is relatively concise and avoids unnecessary words, though improved structuring could enhance readability.

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?

Despite having 6 parameters and no output schema, the description only covers the disabled state. It lacks information on parameters, successful usage, expected output, and return format, making it incomplete for an agent to use the tool when enabled.

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 0%, and the description does not mention any of the 6 parameters (reason, acknowledgePlaintext, reference, vaultId, itemId, fieldId). It provides no guidance on what they mean or how to use them.

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 states that plaintext reveal is disabled, implying the tool would reveal secrets, but it primarily focuses on failure rather than clearly stating the tool's core function. It fails to provide a concise verb+resource purpose.

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?

The description explicitly advises not to call this tool under current conditions and suggests alternatives (restarting with flags, using script runner). It provides clear when-not-to-use guidance, though it lacks explicit when-to-use scenarios.

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