apply_moves

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

No annotations provided, so description carries burden. It discloses core actions (create, move, delete) and dry_run behavior, but omits details on error handling, idempotency, or return format beyond 'previews counts'.

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 concise sentences with no redundant information. Front-loaded with the core purpose, and each sentence adds essential detail.

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?

Given no output schema, the description partially addresses return values ('previews counts') for dry_run but not for actual runs. Lacks information on atomicity, success/failure reporting, and what the function returns after execution.

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%, so description must explain parameters. dry_run and delete_junk are explained; file_path is implied as the TSV path but not explicitly linked. Two of three parameters are clarified, one is left implicit.

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?

Description clearly states the action (apply a catalogue plan TSV) and resources (creates folders, moves bookmarks). It differentiates from single-operation siblings like move_bookmark and create_folder by implying batch processing, though not explicitly naming them.

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 context for dry_run and delete_junk options, but lacks explicit guidance on when to use this tool versus alternatives (e.g., move_bookmark for single moves). No exclusions or prerequisites mentioned.

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