Contract Testing: Delete Integration

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

The annotations already carry destructiveHint=true and readOnlyHint=false, so an agent knows this is a mutation. The description adds no behavioral context beyond the word 'Delete'—it does not state whether deletion is permanent, whether it cascades to related contracts/webhooks, or what permissions are required. With no extra behavioral disclosure beyond annotations, this is a gap.

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 purpose sentence is front-loaded and concise, but the 'Parameters' section merely duplicates the schema's parameter names and descriptions. The 'Toolset' line adds marginal context. The overall size is small, yet some content is redundant rather than earning its place.

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 two-parameter delete operation with annotations covering destructiveness, the basics are present: what resource is deleted and which identifiers to pass. However, there is no output schema and no description of post-conditions, irreversibility, or relationship to delete_all_integrations, so an agent's understanding of consequences is incomplete.

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 100%, so the input schema fully documents both providerName and consumerName. The description only repeats that information verbatim, adding no further meaning about formats, allowed values, or how the parameters identify the integration. Baseline 3 applies because the schema carries the load.

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 first sentence uses a specific verb ('Delete') and resource ('specific consumer-provider integration'), and the word 'specific' distinguishes it from the sibling contract-testing_delete_all_integrations. It does not, however, explicitly contrast with the other delete_* siblings (e.g., delete_environment, delete_webhook), so it stops short of full sibling differentiation.

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 explicit guidance is given on when to use this tool versus alternatives. The word 'specific' implies it is for deleting one integration rather than all, but the description never names the alternative (delete_all_integrations) or states when not to use it. There are no context signals such as prerequisites or side conditions.

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