Force-delete datastore

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

Beyond the destructiveHint annotation, the description discloses that the cluster and its data are destroyed irreversibly and that protection mode blocks execution. It also communicates that confirm is a mandatory safety gate. This is exactly the behavioral context an agent needs.

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?

Three short sentences deliver the action, scope, consequences, and blocking conditions without redundancy. The most important information is front-loaded in the first sentence.

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 no output schema, this definition covers the essential operational facts: what is deleted, who can do it, irreversibility, required confirmation, and the protection-mode blocker. Nothing critical is missing for an agent to invoke it safely and correctly.

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 already provides 100% coverage with clear descriptions for both parameters. The description adds useful semantic scope by clarifying that datastore_id can refer to any user's datastore and reinforces confirm's mandatory role, though some of this restates schema information.

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 names a specific verb (FORCE-DELETE), a specific resource (any user's datastore), and an authorization scope (as admin). This clearly distinguishes it from the read-only admin tools like ccx_admin_get_datastore and ccx_admin_list_datastores.

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?

It explicitly states the preconditions: confirm must be true, and the operation is blocked while CCX_PROTECT protection mode is on, so an agent knows when the call will fail. It establishes clear admin-only scope, though it does not explicitly mention alternative tools or when a non-force path should be preferred.

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