batch_move_documents

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

Discloses sequential processing, error continuation, automatic rate limiting, and child document movement. Annotations (destructiveHint=true, idempotentHint=true) are not contradicted; description adds valuable behavioral context beyond annotations.

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?

Well-structured with clear sections, use cases, and parameter list. Concise yet comprehensive; every sentence adds value without redundancy.

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?

Description covers purpose, usage, behavior, parameters, and return type (summary with success/failure). With output schema present, return value is adequately described. No gaps given tool complexity.

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 0% (no descriptions in schema); description compensates fully by explaining each parameter, noting optionality of collection_id and parent_document_id, and stating requirement to specify at least one of them.

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?

Clearly states it moves multiple documents to a different collection or parent, with specific verb 'Moves' and resource 'documents'. Distinguishes from siblings like 'move_document' (single) and batch tools for different 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?

Explicitly lists use cases (reorganize, move between collections, restructure hierarchies) and suggests batch size (10-50). Does not explicitly exclude single moves, but the sibling 'move_document' implies alternative. Lacks explicit 'when not to use' but still clear.

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