bulk_edit_documents

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

With no annotations, the description carries full behavioral burden. It usefully discloses that 'delete_tag' is system-wide and permanent, and that 'delete' permanently deletes documents and needs confirmation. But it remains silent on side effects, permissions, or reversibility for the remaining methods (set_permissions, merge, split, reprocess, etc.).

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 tight sentences: purpose first, then method distinction, then destructive warning. Nothing is wasted, though given the tool's breadth it is arguably too sparse rather than too long.

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 18 parameters, 14 methods, nested objects, no annotations, and no output schema, the description is substantially incomplete. It covers only a fraction of the method semantics and parameter meanings an agent would need to invoke it correctly.

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 only 22%, so the description must compensate. It explains the distinction between two method values but adds no meaning for core parameters like 'tag', 'documents', 'pages', 'storage_path', or most of the 14 enum methods, leaving most parameters undocumented.

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?

States a specific verb+resource ('Perform bulk operations on multiple documents'), which clearly separates it from single-document siblings like update_document and from other bulk tools. However, it does not enumerate what kinds of operations are available beyond the two tag methods it calls out, so it stops short of full sibling differentiation.

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?

Provides explicit guidance for choosing between two similar methods ('remove_tag' vs 'delete_tag') and warns that 'delete' requires confirmation, which is useful. But it gives no guidance on when to use this bulk tool versus other tools, and no context for the other 11 methods.

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