Reorder workouts

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds valuable behavioral detail: it clarifies the operation affects only display order and requires the complete set of workout IDs. This reduces ambiguity about side effects and prerequisites.

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 sentences front-load the purpose and immediately follow with the key usage instruction. Every sentence earns its place, with no filler.

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 reordering tool with full schema coverage and good annotations, the description explains the scope, the required input, and the limits of the operation. No significant gaps remain for an agent to use it correctly.

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 schema already covers both parameters, but the description adds crucial semantics for workout_ids: they must include every workout ID for that day and come from tp_get_workouts. This enhances the schema's 'desired display order' by specifying the required completeness and source.

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 action ('Reorder') and the resource ('workouts displayed on a single day'), and explicitly distinguishes it from other tools by noting it only changes display order, leaving dates and content untouched. This distinguishes it from sibling tools like tp_update_workout.

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 provides clear when-to-use context: reordering workouts on a day, and explicitly instructs to pass every workout ID from tp_get_workouts. It does not explicitly name an alternative tool, but the 'Changes display order only' exclusion provides implicit guidance for when not to use it.

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