delete_secret

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

With no annotations, the description reveals deletion behavior and permission requirement, but lacks details on side effects (e.g., irreversibility, cascading deletes) or error handling.

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, front-loaded sentence that conveys the essential action and a key prerequisite. No superfluous words.

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 simple delete tool with one parameter and no output schema, the description covers the basic action and a requirement. However, it lacks details on idempotency or handling of missing secrets, leaving some context gaps.

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?

The description says 'by name', which implies the parameter is a name, but does not elaborate on format or constraints. Schema has no description, so the description adds minimal value beyond identifying it as the identifier.

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 verb 'delete' and the resource 'secret by name', which distinguishes it from sibling tools like get_secret, list_secrets, etc. The purpose is immediately understandable.

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?

It mentions 'Requires allowlist', giving a precondition, but does not specify when to use this tool vs alternatives (e.g., set_secret). No guidance on when not to use it.

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