delete_user

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

Explicitly labeled '[DESTRUCTIVE]' and states 'Cannot be undone' and 'Permanently deletes', fully disclosing the irreversible, destructive behavior. With no annotations provided, the description adequately carries the burden.

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 sentences, each valuable. Front-loaded with destructive warning. No redundant or unnecessary words. Perfectly concise.

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?

Lacks details about return behavior or error handling. For a tool with no output schema, a note on success response (e.g., 'Returns success message') would improve completeness. Otherwise adequate.

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 a clear description and example for the 'ids' parameter. The description reinforces array usage but adds minimal new meaning beyond the schema.

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 clearly states the action ('deletes'), the resource ('3CX users'), the method ('by their numeric Ids'), and marks it as permanent. It distinguishes from sibling tools like get_user and list_users.

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?

Provides clear guidance: warns of irreversibility, instructs to get IDs from get_user or list_users first, and notes that it accepts an array for batch deletion. Does not explicitly list when not to use, but the destructive nature implies caution.

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