create_collections_by_id_batch_remove

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

Annotations already indicate readOnlyHint=false and idempotentHint=true, and the description adds little beyond that. It says 'act on batch remove' but doesn't disclose what gets removed, whether it's reversible, or any side effects. The wording is confusing and doesn't clarify the operation's nature.

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 short but poorly structured: the first sentence is confusing ('Create or act on batch remove'), and important context is buried. It doesn't front-load the key purpose and provides only a generic schema-reading note.

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 tool with an unstructured body and no parameter documentation, the description is insufficient. It tells the agent to look elsewhere for fields, but doesn't provide enough context about the operation's effect or prerequisites. The output schema exists, but the description doesn't leverage it.

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?

With 0% schema coverage, the description must compensate, but it only labels id as 'Path parameter' and body as 'Request payload' without explaining required fields or structure. The advice to read the schema is not a substitute for semantic description.

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 says 'Create or act on batch remove' which is vague and misleading; it doesn't clearly state that this tool removes items from a collection. The endpoint path hints at batch removal, but the purpose is not articulated distinctly from siblings like batch_add or delete_collections_by_id.

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?

Only guidance is 'Read the matching GET or the /schema endpoint first' – it tells the agent to consult external resources but doesn't explain when to use this tool vs. single-item delete or batch add. No alternative tools are mentioned or excluded.

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