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

Annotations only declare destructiveHint=false. The description adds real behavioral detail beyond that: create appends at the end of the pipeline, and reorder consumes every stage id in the account. It doesn't mention permissions or what happens on a partial/incorrect reorder payload, so it stops short of a 5.

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?

One dense, front-loaded sentence covering all three actions plus the two sibling redirects. No filler and no repetition of the title.

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?

No output schema exists, and the description adequately covers all actions, their required inputs, and routing. Minor gaps remain around error/partial-reorder behavior and required permissions, but nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description adds the provenance pointer 'ids from get_account_setup' and reinforces the append-at-end semantics for create, which the schema does not convey.

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 three specific operations (add at end, rename/recolor by stage_id, reorder all stages) against a concrete resource. It explicitly distinguishes itself from the similarly named update_stage and delete_setup_item, so an agent can pick correctly without opening schemas.

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?

Names the two nearest alternatives and the conditions that select them: 'To move a lead to a stage use update_stage; to delete a stage use delete_setup_item.' Each action's scope is also stated inline, leaving nothing to inference.

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