delete_connection

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

The description only states the action ('Delete'), implying a destructive operation, but does not elaborate on side effects, required permissions, or reversibility. With no annotations provided, the description fails to disclose critical behavioral traits beyond the basic action.

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 a single sentence that is concise and front-loaded. Every word is necessary; there is no redundancy or fluff. It effectively communicates the core action in minimal space.

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 delete operation with one parameter, the description tells what it does but not what the result or return value is. An output schema exists but is not described. While low complexity reduces the need for extensive context, lacking info on success/failure or response structure leaves a gap.

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 input schema has a single required parameter 'object_id' (integer) with 0% schema description coverage. The description adds that the ID is numeric, but this largely restates the schema type. It does not explain where to obtain the ID or the format. Baseline for low coverage is 3, and the description adds minimal value.

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 explicitly states 'Delete a CDV data connection by its numeric ID.' It uses a specific verb and resource, clearly distinguishing it from sibling delete tools for other entities like datasets or groups. The inclusion of 'CDV data connection' makes the target unambiguous.

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 (e.g., when to update vs delete, or prerequisites like existence of the connection). The sibling list includes many connection-related tools, but the description offers no context for appropriate usage.

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