mysql_drop_user

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

With no annotations, the description carries full burden. It discloses that deletion is not immediate and requires a token, which is a key behavioral trait beyond the tool name. However, it omits details like token expiration, error conditions, or side effects (e.g., privilege cleanup).

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 single sentence is concise and front-loaded with the action, but it underspecifies critical details. It is not wasteful but trades completeness for brevity, earning a mid-range score.

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 two-step deletion process (implied by 'request deletion' and 'confirmation token'), the description lacks context about how to proceed after receiving the token, what user/host refer to, and failure scenarios. It is incomplete for a mutation tool with no output schema or annotations.

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 description does not explain the 'user' and 'host' parameters. It adds no meaning beyond the schema's existence. Parameter names alone are insufficient without context.

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 verb 'request user deletion' and mentions the notable output 'short-lived confirmation token', clearly distinguishing it from sibling tools like mysql_create_user or mysql_drop_database. It could explicitly mention 'MySQL' but the tool name implies it.

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 on when to use this tool vs alternatives, such as prerequisites (e.g., admin privileges) or relationship to mysql_confirm_task for the token. The description does not clarify whether to use this before confirmation or after.

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