Delete website database

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

The description adds valuable behavioral context beyond the annotations: the deletion is permanent, removes all data including users, and is idempotent so deleting a non-existent database succeeds without error. This fully discloses the destructive nature and the idempotency edge case.

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 two sentences with no filler. The first sentence states the core action and scope, and the second sentence clarifies the important idempotent behavior. 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?

For a simple two-parameter delete operation with no output schema, the description is complete. It covers the destructive outcome, the resource type, the scope, and the idempotent behavior, giving an agent everything needed to invoke it correctly.

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 100%, and both parameters, website_uid and database_name, already have clear descriptions. The tool description itself adds no additional parameter semantics, so the baseline score of 3 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 clearly states what the tool does: permanently deletes a MySQL database and all its data from an Agency Plan website, including its users. The verb 'deletes' plus the specific resource (MySQL database) and scope (Agency Plan website) make the purpose unambiguous and distinct from sibling tools like database user deletion.

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: when a database needs to be removed from an Agency Plan website. However, it does not explicitly compare against alternatives such as deleting a database user or deleting the website itself, and it offers no when-not-to-use guidance.

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