delete_integration

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It merely states 'Delete' without mentioning side effects (e.g., irreversible data loss), required permissions, or the role of the optional 'confirmation' parameter. The agent has no insight into what happens during deletion.

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 a single sentence, which is concise and front-loaded with the main verb and object. However, the brevity comes at the cost of missing crucial details. It is not overly verbose, but it sacrifices informativeness for conciseness.

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 has 3 parameters, no annotations, and no output schema, the description should provide substantial context. It does not cover return values, error scenarios, or the effect on related resources. The description is inadequate for an agent to understand the tool's full behavior without additional knowledge.

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%, meaning parameter descriptions are just titles. The tool description adds no information about parameters beyond their names and types. The 'environment' and 'integration_id' are required but unexplained; 'confirmation' is optional with default empty, yet its purpose is unclear. The description fails to compensate for the lack of schema detail.

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 'Delete a Nango integration' clearly identifies the action (delete) and resource (Nango integration). It is specific enough to differentiate from sibling tools like create_integration or list_integrations. However, it does not elaborate on what constitutes an integration in this context, but the core purpose is clear.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., integration must exist) or conditions that would prevent deletion. The description lacks any context about appropriate use cases or when not to use it.

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