mirrored_database_delete

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

The description matches the annotations: destructiveHint=true and readOnlyHint=false. However, it adds no behavioral detail beyond what the annotations already convey, such as irreversibility, cascade effects, or what happens to the underlying mirroring data.

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 a single, front-loaded sentence with no wasted words. For a straightforward destructive operation, this level of conciseness is appropriate.

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?

The description is minimal but sufficient to identify the operation, and the schema covers the required parameters. However, for a destructive tool with no output schema, it lacks useful context about side effects, reversibility, or behavior if the database does not exist.

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 description coverage is 100%, so both parameters are already documented by the input schema. The description adds no further parameter context, which is acceptable given the schema's completeness.

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 specific verb 'delete' and the exact resource 'mirrored database', making the tool's function immediately clear. This distinguishes it from sibling tools that operate on other resource types and from mirrored_database_get/update/start_mirroring operations.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that stopping mirroring is a non-destructive alternative, nor does it clarify prerequisites or situations where deletion is appropriate.

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