delete_connection

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only describes the action as 'Delete' without mentioning irreversibility, side effects on related data, or whether confirmation is required (despite a 'confirmation' parameter). This is insufficient for an agent.

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?

While extremely concise (one short sentence), it is under-specified to the point of being unhelpful. The description does not earn its place by providing essential context; it merely restates the tool's name.

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 simplicity of the action (one delete operation) but with 4 parameters and no annotations or output schema, the description is incomplete. It should explain the environment context, the meaning of the confirmation parameter, and the irreversible nature of the 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 0% (no parameter descriptions in schema), yet the description adds no explanation for any of the 4 parameters, including the optional 'confirmation' field that likely has significance. The description fails to compensate for the schema gap.

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 clearly states the verb 'Delete' and the resource 'one Nango connection', making the purpose unambiguous. It distinguishes from sibling tools like 'create_connect_session' by specifying a destructive action.

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 guidance on when to use this tool vs alternatives, prerequisites (e.g., connection must exist), or when not to use it. The sibling list includes many creation and retrieval tools, but no context for differentiation is provided.

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