Move Entry

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

Annotations already declare destructive and idempotent hints. The description adds valuable details: the copy-verify-delete sequence and rollback on failure, which goes beyond the annotation flags. No contradiction.

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?

One sentence, 18 words, front-loaded with the action. Every word serves a purpose; no 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?

The core behavior is explained but missing parameter semantics and return value details. Given no output schema and 5 parameters, the description is somewhat incomplete but adequate for a simple move operation.

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 0%. The description only implies source and target via 'source' and 'destination' but doesn't explain the 'confirm' boolean or 'target_tag_ids'. The agent lacks critical info on how to correctly set parameters, especially whether confirm=true is required.

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 uses a specific verb 'Copy... delete' to describe a move operation, clearly distinguishing it from 'duplicate' (copy without delete) and 'delete' (delete without copy). It identifies the resource (entry) and the two bundles involved.

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?

The description implies a move operation but doesn't explicitly state when to use this tool over alternatives like bundled_duplicate_entry or bundled_move_kanban_entry. No exclusions or alternative guidance provided.

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