delete_mcp_integration

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

Disclosed irreversible, immediate removal of access, and cascading deletion of servers. Annotations already indicate destructiveHint=true, but description adds concrete behavioral details beyond 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?

Two sentences, front-loaded with action and scope, followed by consequences and caution. No redundant or unclear wording.

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 tool's simplicity (one param, no nested objects, output schema exists), the description adequately covers purpose, effect, and caution. No missing info needed for correct invocation.

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% for the single parameter ('id'), so description does not need to add param details. It adds no extra meaning beyond the schema's 'MCP integration ID or slug'.

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?

Description clearly states 'Delete an MCP integration and all servers beneath it', a specific verb+resource+scope. Distinguishes from sibling delete tools for other resources and from create/update tools.

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?

Provides explicit caution: 'should only be used after confirming nothing depends on the integration'. This instructs when not to use it, though it does not mention alternatives like 'delete_mcp_server' for partial deletion.

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