Reorder Tasks

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

Annotations already indicate non-destructive, non-read-only behavior. The description adds 'reorder' but does not disclose side effects, permission requirements, or behavior if task list is incomplete. With annotations present, a score of 3 is appropriate as the description adds minimal behavioral context beyond the annotation hints.

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 one sentence, front-loaded with the core action, and contains no unnecessary words. It efficiently conveys the purpose and required input, though could be slightly expanded for completeness.

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?

For a straightforward reorder action, the description covers the main intent and parameter usage. However, it omits details about what happens if some task numbers are missing, whether the reorder is relative or absolute, and what the return value is. Given no output schema, these gaps affect completeness.

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?

Input schema descriptions already cover both parameters (cardId and taskNumbers with 'All task numbers in desired order'). The description repeats this without adding new meaning or constraints beyond the schema, so baseline 3 is justified given 100% schema coverage.

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 'Reorder tasks in a card' with a specific verb and resource, distinguishing it from sibling tools like add_subtask, delete_task, or move_task. It also instructs to provide all task numbers in desired order, making the action unambiguous.

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 basic instructions ('Provide all task numbers in the desired order') but offers no guidance on when to use this tool versus alternatives like move_task or batch operations. It does not exclude cases where the user might only want to move a single task or omit task numbers.

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