Contract Testing: Delete All Integrations

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

The description aligns with annotations (destructiveHint=true, idempotentHint=true) but does not add extra behavioral context beyond stating 'Delete ALL'. While annotations cover the core traits, additional details about what exactly gets deleted (all integrations in workspace) are already in the purpose.

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 extremely concise—two sentences plus a toolset line—with no redundant information. Every word adds value, and the key action is front-loaded.

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?

While the description covers the basic action, it lacks warnings about irreversibility or impact. Given the destructive nature and no parameters, more contextual completeness (e.g., confirmation prompt or scope) would be prudent, but the score is adequate for a simple tool with good annotations.

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 zero parameters and 100% schema coverage, the description correctly states 'Parameters: None', making it clear there is no input required. This meets the baseline for no-parameter tools.

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 tool deletes ALL consumer-provider integrations in the workspace, using a specific verb-resource combination. It distinguishes from the sibling tool 'contract-testing_delete_integration' which deletes a single integration.

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?

No guidance is provided on when to use this tool versus alternatives like deleting individual integrations. There is no mention of prerequisites, risks, or situations where this bulk deletion is appropriate.

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