Move Action Plan Item Within Or Across Sections

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

Annotations already declare non-readonly and non-destructive. The description adds that it creates a new Action Plan Item (HTTP 201) but ambiguously says 'Action Plans' and does not clarify that the original item is removed/moved. Adds some value but incomplete.

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?

Description is concise with front-loaded action. However, it contains a typo ('move action action') and includes redundant API details. Still efficient overall.

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 the tool's complexity (moving items between sections) and the presence of annotations covering safety, the description adequately covers purpose, required params, and return value. Missing explanation of optional param and original item behavior, but overall complete.

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 100%, so baseline is 3. Description lists required parameters (already in schema) but does not explain the optional 'next_plan_item_id' parameter, missing an opportunity to add meaning.

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 states 'Move Action Plan Item within or across Action Plan Sections' with a specific verb ('move') and resource ('Action Plan Item'). It distinguishes from siblings like 'move_action_plan_section' by specifying item-level movement.

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 provides clear context: moving items within/across sections and lists required parameters. However, it does not explicitly state when not to use or contrast with alternatives like reordering, but the context is sufficient.

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