Delete database

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

The description merely repeats the action 'Delete', which is already indicated by the tool name and annotations (destructiveHint=true). It adds no additional behavioral context, such as irreversibility, confirmation requirements (handled by schema), or consequences (e.g., data loss). With annotations already covering the destructive nature, the description should provide extra detail beyond the schema.

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 of 9 words, which is concise. However, it is not front-loaded with critical information (e.g., the need for confirmation). There is no structure beyond a simple declarative statement. Every word earns its place, but more context could fit without harming conciseness.

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 simple nature of the tool (3 required parameters, no output schema, annotations present), the description is minimally adequate. It explains the basic action, but lacks details on behavior (e.g., what happens if the database doesn't exist, whether deletion cascades). For a destructive operation with siblings, it could be more complete.

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 100%, and each parameter has a description in the schema (database cluster ID, database name, confirm boolean). The tool description adds no additional meaning or context for the parameters. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Delete a database') and the resource ('from a database cluster'). It is a specific verb+resource combination. However, it does not differentiate from sibling tools like 'delete_database_cluster' or 'delete_database_snapshot', which could cause confusion for an agent selecting 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?

No guidance is provided on when to use this tool versus alternatives (e.g., deleting a database cluster vs. a snapshot). The description does not mention prerequisites, context, or exclusions. The agent receives no help in decision-making.

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