Delete indexed documents

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

Annotations already flag destructive and idempotent, but the description adds real value beyond them: chunks and vectors are removed together, the effect is irreversible, and a selector is mandatory. It does not describe what happens to non-matching documents or any partial-failure behavior.

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 short sentences, front-loaded with what is deleted and how it is selected, then the side effect, then the hard constraint. No filler.

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 mutation tool with no output schema, annotations plus description cover safety (destructive/irreversible), scope (scoped selectors), and side effects (chunks/vectors). The main omission is the collection-wide 'all' path, which overlaps ambiguously with the sibling drop_collection.

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 schema already documents all five parameters, making 3 the baseline. The prose names the selector kinds (id, exact uri, path prefix) but omits the collection default and the collection-wide 'all' flag, adding little 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?

Specific verb (Remove) plus resource (documents from a collection) and the three selector modes. It is clear this is a scoped document deletion, distinct from list_sources/list_collections, though it never contrasts itself with drop_collection or explains the collection-wide "all" mode the schema exposes.

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 precondition 'requires at least one selector' tells the agent how to invoke it validly, and 'irreversible' warns of consequence. However it gives no when-to-use vs. siblings (drop_collection for whole collections) and no guidance on choosing between id, uri, and prefix selectors.

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