reorder_sections

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

With no annotations provided, the description carries the full burden. It discloses that the operation is batched and deterministic, but it does not mention potential side effects (e.g., unlisted sections shifting), permissions, or reversibility. The schema provides more detail but the description itself remains vague.

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 two sentences with no filler, front-loading the primary action. Every word serves a purpose, making it highly concise and well-structured.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not mention return values, error behavior, or the effect on sections not listed in the array (only hinted at in the schema). The tool's complexity is moderate, but the description underspecifies essential context.

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 50%, and the description does not compensate. It repeats the array structure but adds no meaning beyond the schema's existing order description. The course_id parameter is entirely unexplained, and the description omits details like 0-indexing or behavior for omitted sections (both present only in the schema).

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 identifies the action (reorder) and the resource (sections in a course), distinguishing it from sibling section tools like create_section, update_section, or hide_section. The mention of a batched call reinforces its specific purpose.

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 it is for bulk reordering ('in one batched call') but does not explicitly state when to use this tool over alternatives, nor does it name any alternative. It gives no negative guidance or exclusions.

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