delete_integration

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive operation, but there is no mention of irreversibility, required permissions, cascading effects, or what happens to associated data. The description is silent on all behavioral aspects.

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 extremely concise (six words), which is efficient, but it lacks substantive content that would justify its brevity. It is not bloated, but it is too minimal to be genuinely useful.

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 mutation with two required parameters and no output schema, this description is critically incomplete. It fails to specify return behavior, error conditions, or deletion semantics, leaving the agent to guess about critical execution details.

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?

The description adds no meaning to the parameters 'environment' and 'integration_id'. With schema coverage at 0%, the agent receives no explanation of what these values represent, any format constraints, or how they relate to the deletion. The schema alone is insufficient.

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 states a specific verb ('Delete') and a clear resource ('a Nango integration'), making the tool's basic purpose unambiguous. It is distinct from sibling tools like delete_connection by referring to 'integration', though it does not elaborate on scope (e.g., integration definition vs. instances).

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 instead of alternatives such as delete_connection or update_integration. No context, prerequisites, or conditions for use are provided.

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