todoist_sections_reorder

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

No annotations are provided, so the description carries full burden. It states the action ('reorder') but does not disclose side effects (e.g., impact on tasks within sections), permissions needed, or whether the operation is reversible. For a mutation tool, this is minimal transparency.

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 (10 words), front-loaded with the verb and resource, and contains no unnecessary information. Every word serves the purpose.

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 simple reorder tool with 2 required parameters and no output schema, the description adequately covers the basic purpose. However, it lacks details on how reordering works when positions conflict or if there are constraints, leaving some gaps for a robust understanding.

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?

The input schema has 100% coverage, and the description does not add meaning beyond what the schema already provides (e.g., 'specifying their new positions' is implied by the 'sections' array with 'section_order'). Baseline 3 is appropriate.

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 uses a specific verb ('reorder') and resource ('sections within a project'), clearly distinguishing it from sibling tools like 'todoist_section_move' (which likely moves sections to different projects) and 'todoist_section_create/delete/update'.

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 implies when to use (to change section order) but does not explicitly state when not to use or mention alternatives like 'todoist_section_move' for moving sections to different projects. The context is clear but not formally guided.

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