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

Annotations already declare destructiveHint=true, so the destructive nature is known; the description adds the non-obvious mechanics that deletions land on the open branch as unsaved changes reviewed and saved in Xodia, plus partial-failure behavior for unknown slugs. Plan-limit context (Free: 2 collections / 100 items) is useful for batch sizing, though permission requirements and confirmability are only partly covered.

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 core semantics are front-loaded in a strong opening sentence, and the confirmation and branch-write sentences earn their place. The closing sentence drifts into plan-tier and folder-conversion details ('turning a folder into a Xodia collection needs a paid plan') that are irrelevant to invoking a delete, diluting an otherwise tight definition.

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 four-parameter tool with no output schema, it covers the essentials: what is deleted, how failures are reported ('slugs not found are listed'), where writes land, and that user confirmation is expected. Missing only explicit auth/permission requirements and a clear statement of what a successful response contains.

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 75%, so most parameters are already documented, including the branch default and the provenance hints for projectId and collection. The description restates the 100-item cap and branch behavior already implied by the schema and adds little new meaning for 'slugs' or 'collection' beyond what the patterns and descriptions supply.

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 first sentence names a specific verb and resource and adds scope: 'Deletes up to 100 items by slug; slugs not found are listed.' That is clearly distinct from siblings like delete_file, delete_folder, and update_item, though the distinction is carried by the resource noun rather than an explicit sibling callout.

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 gives one concrete usage rule — confirm with the user before deleting content they wrote — which is genuinely actionable. However, it never names an alternative (e.g. update_item for edits, delete_file/delete_folder for non-item content) or states when a batch delete should be split or avoided, leaving routing to inference.

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