directus_delete_items

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

With no annotations provided, the description carries the full burden. It successfully discloses the critical safety trait that the action is 'irreversible,' but omits other important behavioral details such as cascade delete behavior, partial failure handling, or return value structure.

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 consists of two efficient sentences with zero waste. The first sentence establishes purpose and scope, while the second provides essential safety information. Every word earns its place.

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 with three completely undocumented parameters (0% schema coverage) and no output schema, the description is insufficient. It lacks explanation of what constitutes a 'site' or 'collection,' and does not describe the return value or success indicators.

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?

Given 0% schema description coverage, the description must compensate for three undocumented parameters. It only partially addresses this by mentioning 'IDs,' which maps to the 'keys' parameter, but fails to explain the 'site' or 'collection' parameters or the expected format of the ID array.

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 specific action (Delete), resource (items), and scope (multiple by their IDs). The plural 'items' effectively distinguishes this from the sibling tool 'directus_delete_item' (singular), clarifying this is for bulk 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 implies usage through the phrase 'multiple items,' suggesting it should be used for bulk deletion rather than single-item deletion. However, it lacks explicit guidance on when to prefer this over 'directus_delete_item' or prerequisites like required permissions.

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