remove_documents_bulk

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

No annotations are provided, so the description carries full burden. It states 'Remove multiple documents', which implies destructive behavior, but it does not clarify whether removal is permanent, any permissions needed, or side effects (e.g., cascading deletions). The description is minimally transparent.

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 is very concise (two sentences) with no waste. The first sentence front-loads the core purpose, and the second sentence adds context. Every word is meaningful.

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?

The description provides basic purpose but lacks details on behavior when both parameters are provided, error handling for empty inputs, or return value (e.g., number removed). Given that the tool has no required parameters and no output schema, more completeness would be beneficial. It is adequate but not comprehensive.

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 100%, so baseline is 3. The description adds nuance by stating 'by IDs or tags', implying mutual exclusivity (either/or), which goes beyond the schema's simple lists. This adds moderate value, justifying a score of 4.

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 ('Remove multiple documents'), the resource, and the criteria ('by IDs or tags'). It also includes a usage context ('cleaning up the knowledge base'), which adds to purpose clarity. The sibling 'remove_document' is implicitly differentiated by the 'bulk' aspect.

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 mentions it is 'useful for cleaning up the knowledge base', which gives a context for use, but it does not explicitly state when not to use it or mention alternatives like 'remove_document' for single removals. The guidance is vague and lacks exclusions.

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