Delete user

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description adds crucial behavioral context: 'This cannot be undone' highlights irreversibility, and 'blocked while protection mode (CCX_PROTECT) is on' discloses a precondition. This goes well beyond the annotations and helps the agent understand side effects and constraints.

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 three sentences, each earning its place: the action, the key constraints, and the alternative. It is front-loaded with the core purpose and contains no redundant or promotional language.

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 the tool's complexity (2 required params, no output schema) and the annotations, the description covers the essential information: irreversibility, confirmation requirement, and protection-mode blocking. It also suggests an alternative tool, making the context complete for an agent to call it 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add new meaning to the parameters beyond what the schema already states—confirm's 'Must be explicitly true' is restated, and user_id's format is left to the schema. No additional parameter semantics are provided.

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 starts with a specific verb and resource: 'Delete a CCX user account.' This clearly states the tool's function and distinguishes it from siblings like ccx_admin_delete_datastore. It also names an alternative (ccx_admin_suspend_user), reinforcing the specific purpose.

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 provides explicit when-to-use guidance: it states the action, the requirement for confirm=true, and the protection-mode block. It also directs the agent to consider ccx_admin_suspend_user as an alternative, which clarifies the choice between delete and suspend.

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