mysql_drop_database

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

With no annotations, the description carries the full burden. It discloses that the tool is destructive ('deletion') and that it returns a short-lived token, implying the action is not immediate and requires confirmation. This is good transparency for a simple tool, though it could mention that the database is not actually dropped until confirmation.

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?

A single sentence of 11 words that efficiently conveys the essential information. No superfluous language; 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 tool with one parameter and no output schema, the description is complete enough. It covers the purpose, the two-step nature, and the token output. Could mention existence requirements or error conditions, but not lacking for minimal viability.

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%, and the tool description does not describe the 'database' parameter. However, the parameter name is self-explanatory given the tool purpose. The description adds no additional semantic value beyond the name.

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 ('Request database deletion') and the result ('return a short-lived confirmation token'). It effectively distinguishes from siblings by implying a two-step process where this tool initiates deletion and another tool (like mysql_confirm_task) uses the token to confirm.

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 hints at a two-step process by mentioning the confirmation token but does not explicitly state when to use this vs. alternatives or that the token must be used with mysql_confirm_task. No direct guidance on prerequisites or exclusions.

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