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

Annotations already establish it is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds a genuinely useful behavioral constraint beyond the annotations: the list must contain ALL item ids in the new order with no duplicates, which defines the replacement semantics of the call. Auth requirements and error behavior on missing/invalid ids remain unspecified.

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?

Two short sentences, front-loaded with the purpose and immediately followed by the parameter contract. No filler; every clause adds information.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile and idempotency. Given the low-complexity two-parameter shape, the description supplies what an agent needs, missing only error/permission behavior.

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 must carry the parameter burden, and it does: it documents id as a uuid and defines body.itemIds as the complete ordered set of item ids with no duplicates. That is meaningfully more than the raw schema conveys, though it doesn't spell out the array item type (uuid) explicitly.

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?

States a specific verb ('Reorder') and resource ('program stops'), so the operation is unambiguous. It doesn't explicitly contrast itself with the other reorder_* siblings (reorder_slides, reorder_program_info_cards, reorder_trip_items), though the resource name in the tool name conveys the distinction.

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 explains the mechanics but gives no when-to-use or when-not-to-use guidance and never names an alternative tool. Usage must be inferred from the name and the sibling set.

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