delete_connection

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

With no annotations, the description bears the full burden of disclosure. It simply states 'Deletes a connection' without mentioning whether the operation is permanent, requires special permissions, or affects dependent resources. This lack of side-effect information is a significant gap for a mutating 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?

The description is very short, but this is under-specification rather than effective conciseness. It lacks even basic contextual information expected for a delete tool, so it fails to earn its place as a complete description.

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 and the presence of an output schema, some return-value details are unnecessary, but the description still omits crucial context about the operation's effects, reversibility, and preconditions. The single sentence is insufficient for a deletion tool.

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%, and the description does not explain the connection_id parameter beyond what the schema already provides (just a name and type). The description adds no value in clarifying parameter meaning, format, or constraints.

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 the action ('Deletes') and the resource ('connection'), which clearly conveys the core purpose. It distinguishes itself from sibling tools like get_connection, create_connection, and update_connection by being the only deletion operation, though it does not explicitly state the scope or target type.

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 is provided on when to use this tool versus alternatives, prerequisites (e.g., existence of the connection), or situations where deletion might be inappropriate. The usage is implied only by the tool's name and action verb.

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