tasks_move

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

With no annotations, the description bears full responsibility for behavioral disclosure. It merely states 'Move or reorder' without detailing side effects (e.g., impact on subtasks, position semantics, or whether the operation is reversible). The agent is left uninformed about potential behaviors.

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 a single sentence with no unnecessary words. It is concise and to the point, though it could be slightly expanded to improve clarity without sacrificing brevity.

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 description covers the core function but does not fully equip the agent for proper invocation. It omits details about the effect of moving (e.g., changing parent vs. reordering within same list) and does not mention return value. Given the 4 parameters and no output schema, the description is adequate but has gaps.

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 100%, so the input schema already describes all 4 parameters. The description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate since the schema carries the full burden.

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 'Move or reorder a Google Task' clearly identifies the verb (move/reorder) and resource (Google Task). While it distinguishes from siblings like tasks_create or tasks_delete, it could be more explicit about differentiation from tasks_update, which might also involve changing task properties.

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?

No guidance is provided on when to use this tool versus alternatives such as tasks_update, tasks_complete, or other reorder operations. The description lacks context about scenarios (e.g., reordering within a list vs. moving to another list) and does not mention prerequisites or constraints.

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