delete_cloudflow_connection

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

Annotations indicate destructiveHint=true, and the description adds that the tool is destructive ('Deletes a connection') and provides specific behavior: returns 409 if the connection is referenced by one or more flows. This adds value beyond annotations by disclosing a conflict scenario.

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 concise with two sentences. It front-loads the purpose and provides a key behavioral detail without any fluff. Every word earns its place.

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 (delete operation with two parameters), the description is sufficiently complete. It covers the resource type, action, and a relevant error condition. No output schema exists, so return details are not needed. Minor missing context on success response, but acceptable.

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 50% (only customerContext has a description). The description does not mention either parameter or add meaning beyond the schema. For a tool with low schema coverage, the description should compensate but fails to do so.

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 action 'Deletes a connection' on a specific resource 'cloud provider connections used in CloudFlow workflows (AWS and GCP)'. It distinguishes from siblings like create_cloudflow_connection and update_cloudflow_connection by specifying the delete operation.

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?

The description implies when to use the tool (to delete a connection) but does not explicitly state usage context or when alternatives (e.g., update or list) are more appropriate. It mentions a 409 error if referenced, which provides some guidance on a constraint, but lacks explicit when-to-use or when-not-to-use instructions.

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