move_planner_event

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

No annotations are present, so the description carries the full burden. 'Move' clearly implies a mutation, but it does not disclose side effects such as whether the event is removed from its previous location, whether conflicts at the target are possible, or what the response contains.

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 concise, two sentences, and free of unnecessary detail. It communicates the essential purpose and scope without fluff.

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?

With no output schema and a relatively simple operation, the description covers the main purpose. However, it omits guidance on how this differs from reorder_planner_events and does not resolve the 'and/or' ambiguity versus the required date and section parameters.

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%, but parameter names are relatively self-explanatory (event_id, date, section). The description adds that date and section are the target values, but it does not explain that both are required despite 'and/or', nor does it clarify the meaning of section beyond the enum.

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 the action ('Move'), the target resource ('an existing planner event'), and the specific change ('to a different date and/or section'). It also distinguishes from related tools by noting it works for recipe, note, and ingredient events.

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 purpose is implied well enough, but there is no explicit guidance on when to choose this tool over siblings like reorder_planner_events or update_planner_entry_text. It does not mention alternatives or exclusion cases.

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