db_delete_user

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

With no annotations, the description carries the full disclosure burden. It says 'Drop,' which implies destruction, but it does not state irreversibility, permission requirements, or effects on associated databases/privileges. The 'confirm: Required' hint is misleading because the schema marks confirm as optional with a default of false.

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 very short and front-loaded, but it is under-specified rather than appropriately concise. The 'Args' section is minimal and introduces a schema inconsistency.

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 destructive operation with no annotations, the description is incomplete. It does not explain the confirmation semantics, what happens to the user's databases, or whether the action is reversible. The output schema exists, so return-value details are not required, but the missing behavioral and parameter context is significant.

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%, so the description must compensate. It only says 'dbuser: Name' and 'confirm: Required,' adding minimal meaning beyond the schema titles. It does not specify the expected type of confirm or clarify that it must be true to proceed, and it contradicts the schema's required/default configuration.

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 a specific verb and resource: 'Drop a database user.' This clearly distinguishes it from siblings like db_delete (likely dropping a database) and db_create_user.

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 such as db_delete or db_user_get. The only usage-like hint is 'confirm: Required,' but it does not explain when confirmation is needed or what happens without it.

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