verified_batch_move

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

The description discloses the verification and rollback behavior ('rollback hints if verification fails') and includes auth version '[Auth: V2]'. However, no annotations exist, so the description carries full burden. It does not detail side effects, verification criteria, error handling, or whether the wrapper is idempotent.

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 brief (one sentence plus tags), but its brevity sacrifices necessary detail. Given the complexity of a batch move with verification, it should be longer but still clear.

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 tool lacks output schema and parameter documentation. The description only gives a high-level purpose, omitting details on return values, error states, or verification process. This is insufficient for an agent to invoke it correctly without additional context.

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?

The input schema has 0% description coverage, and the description provides no information about the 'moves' parameter structure, required fields, or format. This is a critical gap for a batch operation tool.

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 identifies the tool as a 'Verified batch move wrapper with rollback hints', specifying both the action (batch move) and the added verification/rollback behavior. It also lists related sibling tools, helping distinguish it from alternatives like 'move_tasks' and 'verified_move_tasks'.

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?

While the description mentions related tools and a '[Category: Verified Actions]' category, it lacks explicit guidance on when to choose this tool over siblings such as 'move_tasks' or 'verified_move_tasks'. It does not specify scenarios where verification is required or contraindicated.

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