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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds the key behavioral constraint that the list must include every milestone exactly once, implying a full replacement of order. It doesn't describe failure behavior if the list is incomplete, but the explicit requirement compensates.

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 with no filler. The core instruction is front-loaded, and the critical prerequisite is stated immediately. Every sentence earns its place.

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 two-parameter tool with full schema coverage and no output schema, the description covers the essential context: what to do, what to do first, and the completeness requirement. It doesn't specify error handling for invalid lists, but that's a minor gap given the explicit prerequisite.

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 100%, so the schema already documents both parameters. The description reinforces that 'milestones' must be the complete set in desired order, adding meaning beyond the schema's 'Every milestone on the project' phrasing. 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 states a specific verb ('Put'), a resource ('milestones of a project'), and the exact operation (reorder into the order given). It clearly distinguishes from siblings like reorder_states and update_milestone by focusing on ordering the full milestone list.

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 explicitly instructs the agent to read milestones with list_milestones first and requires the list to name every milestone exactly once. This provides clear when-to-use guidance and a prerequisite, which is strong usage direction.

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