directus_delete_users

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

With no annotations provided, the description carries full behavioral disclosure burden. It appropriately warns that the action is 'irreversible,' but lacks critical context about cascading effects (what happens to user-created content), rate limits, or required authorization headers.

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?

Extremely concise at two sentences. The '[UNIFIED]' prefix appears to be metadata noise rather than helpful content, but the core message is efficiently front-loaded without verbosity.

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 operation on multiple user records, the description is incomplete. It lacks parameter documentation, return value description, error handling guidance, and prerequisites. The warning about irreversibility alone is insufficient for safe agent operation.

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 coverage is 0% with two required parameters (`site` and `ids`), yet the description fails to explain either. It should clarify what `site` refers to (Directus instance identifier) and what format `ids` expects (UUIDs, integers, etc.), especially since the schema items are untyped ({}).

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 (Delete) and resource (multiple users) with a specific verb. However, it fails to distinguish from the sibling tool `directus_delete_user` (singular), leaving ambiguity about when to use bulk vs. single deletion.

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?

No guidance provided on when to use this tool versus the singular `directus_delete_user`, nor any prerequisites like authentication requirements or permission levels needed to delete users.

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