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

Annotations already establish that this is a write (readOnlyHint=false) that is neither destructive nor open-world, so the safety profile is covered. The description adds the important behavioral trait that this is a whole-list replacement — you must supply every column id — which is more than the annotations convey. It stops short of describing permission needs or the effect on cards in the columns.

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, front-loaded sentences with no filler: the operation first, the required input second. 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?

With only two fully documented parameters, no output schema, and annotations covering the safety profile, the description contains what an agent needs to invoke the tool correctly. It would be a 5 only if it clarified what happens to ids omitted from the list.

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 100% and the two parameter descriptions ('All column ids, in the order they should appear', 'Board to reorder') already carry the semantics. The description's wording largely restates this rather than adding new meaning, so baseline 3 applies.

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 and resource ('Set the left-to-right order of the columns'), so the agent knows this is a full ordering operation on columns rather than a property edit. It does not name the neighboring tools it must not be confused with (update_kanban_column, move_kanban_card), so it stops short of a 5.

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 instruction 'Pass every column id of the board' is a genuine invocation constraint that tells the agent when the call is valid. However, there is no statement of when to prefer this over update_kanban_column or move_kanban_card, and no exclusions or prerequisites stated.

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