post_knowledge_base_bulk_move_route

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds nothing beyond that — no note on what happens to existing folders, whether the move is reversible, or required permissions. No contradiction, but no added value either.

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?

A single short phrase — no wasted words and front-loaded — but it reads as a title fragment rather than a purposeful description, and its brevity comes from under-specification rather than disciplined economy.

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 mutating, non-idempotent bulk operation with no output schema and only 50% parameter coverage, the description is too thin. It omits the single-vs-bulk distinction, the meaning and format of move_to, and any behavioral context the annotations don't already carry.

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 50%: document_ids is documented in the schema, but move_to has no description in either place. The phrase 'To Folder' hints that move_to is the destination folder, offering marginal compensation, but its format (ID vs. name vs. null behavior) is left entirely to inference.

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 phrase 'Bulk Move Entities To Folder' gives a verb (move), a scope (bulk), and a destination (folder), which is more than a bare tautology. However, 'Entities' is vague — the schema reveals these are documents or folders — and it never distinguishes itself from the sibling post_knowledge_base_move_route (single move). Adequate but with clear ambiguity.

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?

There is no when-to-use guidance, stated prerequisites, or reference to alternatives despite the existence of a single-move sibling (post_knowledge_base_move_route) and a bulk-delete sibling. The agent must infer the appropriate context entirely.

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