delete_integration

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds little beyond restating the operation and path — it does not say what happens to dependent aliases/values/matchers or whether the removal is reversible, which is the context an agent would actually need here.

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 short fragments, front-loaded with the action and followed by the endpoint. No filler, though the endpoint restates the operation rather than adding new information, making the second sentence low-value.

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 destructive delete with no output schema, the annotations cover the safety signal, but the 0% parameter coverage and the absence of any cascade/attachment behavior leaves an agent without enough to call it confidently in ambiguous cases.

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 0%, so the description must carry parameter meaning; the URL template does show that project_id and integration_id are path identifiers scoping the target resource. However, it adds nothing about identifier provenance (where to obtain an integration_id) or precedence, so compensation is only partial.

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 ("Remove integration") and the REST path confirms it targets a project-scoped integration. It is not explicitly differentiated from the many sibling delete tools (delete_integration_value, delete_integration_alias, delete_integration_matcher), so the agent must infer that this removes the integration itself rather than a sub-resource.

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 when-to-use or when-not-to-use guidance, and no mention of the closely related siblings (delete_integration_value, delete_integration_alias, delete_integration_matcher) or of any prerequisite such as detaching the integration first. The usage is only implied by the tool name.

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