Contract Testing: Delete Secret

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

The description says 'Delete', which implies a destructive action, yet annotations set destructiveHint=false and idempotentHint=true. This contradiction undermines transparency. No additional behavioral traits are disclosed beyond the annotations.

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 very short, front-loading the key action. However, it is minimal and could include more context without becoming verbose. It earns its place but leaves room for improvement.

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?

Given the simple tool, the description lacks completeness due to the annotation contradiction. It does not explain idempotency behavior, success/failure responses, or effect on related data. The minimal information is insufficient for an agent to fully understand the tool's behavior.

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?

With 100% schema coverage, the schema already describes the secretId parameter as a UUID. The description repeats this without adding extra meaning, so it meets the baseline but does not enhance understanding.

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 action ('Delete'), the resource ('secret'), and the identifier ('by UUID'). It distinguishes this tool from sibling tools like contract-testing_create_secret, contract-testing_update_secret, and contract-testing_list_secrets.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or side effects. The context is implied, but there are no explicit exclusions or references to other tools.

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