reorder_subtasks

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

The description discloses behavioral traits: the operation is idempotent (confirmed by annotation), and it explains validation constraints (API rejects partial sets and cross-task references). There is no contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds value beyond annotations.

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 plus a bullet point. It front-loads the purpose and return value, then efficiently explains the key constraint and common errors. Every sentence adds value.

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 is complete for a reorder operation. It explains the required parameters, constraints, and error scenarios. With an output schema present, the mention of return value is sufficient. No gaps are evident.

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 the description carries full burden. It explains the 'ids' parameter meaning: must be the complete list of subtask IDs in desired order. It also implies 'task_id' usage via context. This adds essential meaning that the schema alone lacks.

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 tool's purpose: 'Reorder subtasks under a task.' This directly specifies the verb (reorder) and resource (subtasks under a task). It distinguishes itself from sibling tools like add_subtask, delete_subtask, and update_subtask.

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 gives explicit guidelines: 'ids must be the full set of subtask ids on task_id in the desired order.' It also explains common errors and their fixes, such as partial sets or cross-task references, guiding the agent to use list_subtasks first.

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