Delete database cluster

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

The description adds only 'This is irreversible,' which reiterates the destructiveHint annotation. It does not disclose additional behavioral traits such as cascading deletion of associated databases, required permissions, or impact on running services. While annotations already declare destructiveness, the description could provide richer context.

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 short sentences. It front-loads the action and the key consequence. No extraneous information is present.

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?

The description is adequate for a destructive delete operation but lacks details such as what happens to databases within the cluster, whether the operation is synchronous, or any warnings beyond irreversibility. Given the presence of sibling tools for database-level deletion, more context would help. The absence of an output schema does not require explanation, but completeness could be improved.

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 100% description coverage, meaning the parameters are already documented in the schema. The description adds no parameter-level information. According to guidelines, baseline is 3 when schema coverage is high, so this score is appropriate.

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 clearly: 'Delete a database cluster.' The verb 'delete' combined with the resource 'database cluster' precisely defines the tool's purpose. It distinguishes itself from sibling tools like 'delete_database' which deletes a single database within a cluster, ensuring the agent selects the correct tool.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention that this tool is for deleting an entire cluster, as opposed to deleting a single database using 'delete_database'. It also lacks prerequisites or context about the cluster's state.

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