delete_connection

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

Discloses destructive behavior (deletes) despite no annotations. Could mention irreversibility or cascading effects, but adequate for a delete operation.

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 concise sentences, front-loaded with warning, no wasted words. Structure is optimal.

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?

Covers essential context for a delete tool given no output schema. Could mention existence prerequisite, but not critical due to schema_file confirmation step.

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 coverage is 100%; description adds procedural meaning for schema_file parameter (must read a file first) and confirms connection_id's role, adding value beyond schema.

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 the tool deletes a connection from the Fivetran account, distinguishing it from sibling delete tools like delete_destination or delete_group.

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?

Includes explicit warning that it's destructive and requires user confirmation, providing clear context on when to use. No explicit exclusion of alternatives, but the warning suffices.

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