Delete Database Connection

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

Annotations already mark this as destructive and non-read-only, but the description adds important behavior beyond them: the deletion is a soft delete, it goes through CommandBus, and a guarded confirmation policy applies. This meaningfully clarifies what the tool actually does.

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 sentences with no filler. The primary purpose is front-loaded, and the policy constraint is stated efficiently in the second sentence.

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?

An output schema exists, so return-value details are not required, and annotations cover the destructive safety profile. However, for a policy-guarded delete, the agent still needs to know how to satisfy the confirmation requirement; the description mentions confirmation but does not map it to confirm/confirmation_text, and 'revision' is referenced without a corresponding parameter.

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%, so the description must compensate for the parameters, but it does not explain confirm vs confirmation_text or state that connectionId is required. It hints at workspace and connection binding, but the two confirmation-related parameters remain ambiguous.

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 a specific action (soft-delete) on a specific resource (a saved connection) and is consistent with the title 'Delete Database Connection.' The verb and resource make it distinct from sibling operations like update_connection or create_connection.

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 gives clear policy context: confirmation is required, it must be bound to workspace/connection/revision, and read-only policy rejects deletion. This tells the agent when deletion will be permitted, though it does not explicitly name alternatives.

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