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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation/safety profile is covered structurally. The description adds the non-obvious behavioral fact that deletion is one-sided and leaves the provider still emitting events — a partial-state consequence the annotations cannot express. Irreversibility and behavior on a missing/invalid integration_id are not stated.

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?

Two sentences, the identification of the operation first and the critical caveat second. Every clause carries information an agent needs; nothing is redundant with the title or annotations.

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 destructive 3-parameter tool with full schema coverage and no output schema, the description covers the main gotcha an agent must relay to the user. Remaining gaps (irreversibility, whether dependent resources are affected, error behavior) are minor for a leaf delete operation.

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% and both required parameters (project_id, integration_id) plus the context field are fully documented in the schema. The description adds no meaning beyond them, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Delete a deploy-provider webhook integration.' The resource is distinctive enough to separate it from create_deploy_integration, list_deploy_integrations and test_deploy_integration in the sibling list. It does not, however, name those siblings to make the distinction explicit.

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 provider must be told to stop sending events afterwards — this only removes the QualityMax side' gives clear sequencing context that determines whether the agent should treat this as a complete cleanup. No explicit exclusions or named alternatives are given, so it stops short of a 5.

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