delete database

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds little beyond that. 'Executes verified command v-delete-database' hints at implementation but does not disclose irreversibility, cascading effects, or what happens to associated data. The description carries minimal behavioral context beyond what annotations already provide.

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 with the core operation. However, the second sentence, 'Executes verified command v-delete-database,' adds limited agent-relevant value and uses the ambiguous word 'verified' rather than explaining behavior.

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 tool with three required parameters, the description is too thin. It does not explain the destructive consequences, mention confirm, clarify ownership, or provide any workflow context such as checking with list_databases/get_database first. The annotations and output schema help, but the agent still lacks operational context for safe invocation.

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 only 33%, with user and database lacking descriptions. The tool description does not compensate by explaining what 'user' or 'database' refer to or how they should be formatted. Only the confirm parameter is semantically described in the schema, leaving the other two parameters under-documented.

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: 'Delete a database.' This clearly distinguishes it from sibling list/get tools and from delete operations on other resource types. Mentioning the underlying command v-delete-database reinforces the operation without obscuring 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 is given on when to use this tool versus alternatives, nor are there exclusions or prerequisites. There is no mention of listing/checking the database first, verifying ownership, or when deletion may be inappropriate. The intended use is only implied by the verb 'Delete'.

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