delete_connection

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

No annotations provided, and the description omits critical behavioral traits: whether deletion is permanent, reversible, or cascading; what permissions are needed; or error states (e.g., referencing a non-existent connection).

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 short (one sentence), which is efficient but sacrifices necessary detail. It is not well-structured or front-loaded with key behavioral cues.

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?

Even though the tool has only one parameter and an output schema (not provided), the description fails to explain side effects, return values, or failure modes, leaving the agent underinformed for invocation.

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 only parameter, 'connection_id', has no description in the schema (0% coverage) and the description adds no extra meaning—e.g., format, how to obtain it, 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 'Deletes a connection' is a tautology of the tool name 'delete_connection', providing no additional specificity. It fails to differentiate from sibling tools like 'update_connection' or 'get_connection' (e.g., scope, permanence).

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 versus alternatives (e.g., update_connection, create_connection). No prerequisites, such as requiring the connection to exist or being unused, are mentioned.

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