delete_database

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. For a destructive database operation, it says nothing about permanence, data loss, required permissions, dependencies, reversibility, or expected response. This is a critical gap for a mutation tool.

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 words long. While brief, it is under-specified rather than appropriately concise; it lacks the structure and detail needed for a destructive operation. The brevity fails to earn its place as a useful definition.

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 that this is a destructive operation with no annotations, no output schema, and no parameter documentation, the description is completely inadequate. An agent cannot safely infer correct usage or consequences from it.

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?

The schema has two required parameters, id and type, with 0% description coverage. The description adds no meaning about what id identifies, what type values are valid, or how they relate to database deletion. With low schema coverage, the description must compensate and does not.

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 'Delete database' exactly restates the tool name with no additional specificity. It gives the verb and resource at the most literal level but does not distinguish the operation from any sibling delete tool in the environment. This fits the tautology calibration.

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 list_databases, get_database, or create_database. No prerequisites, no when-not-to-use conditions, and no mention of alternatives are provided.

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