secret_reveal

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

With no annotations, the description carries the full burden. It mentions the tool will fail if not enabled but does not disclose what happens on success, required permissions, or return format. Minimal behavioral context.

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 relatively short (three sentences) and avoids unnecessary text, but it is not front-loaded with core purpose and lacks clear structure.

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?

For a sensitive tool with 6 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the tool's basic function, parameter usage, or return value, focusing solely on server configuration.

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 adds no information about any of the 6 parameters (itemId, reason, fieldId, vaultId, reference, acknowledgePlaintext). The const value for acknowledgePlaintext is not explained.

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 does not explicitly state that this tool reveals a secret in plaintext. It focuses on server configuration and failure conditions, making the purpose vague and only implied by the name.

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 provides negative guidance (when not to use and alternatives like restarting the server) but lacks positive guidance on when to use this tool versus siblings like environment_reveal_variable or password_read.

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