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

The annotations already indicate this is a non-read-only, non-idempotent operation. The description adds meaningful behavioral details beyond those annotations: tasks in removed columns move to the FIRST column, blanks are dropped first, and lists normalizing below two names are refused. This gives an agent a solid sense of side effects without contradicting the annotations.

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?

The description is short and front-loaded: the primary purpose and constraints appear in the first sentence, with behavioral edge cases following compactly. Every sentence earns its place, including the terse 'Pro.' note, which communicates an availability restriction without padding.

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 operation with no output schema, the description covers the essential behavior: replacement, ordering, uniqueness, blank handling, minimum-size refusal, and task migration. It does not explain the return value or error responses, but that is less critical given the simple parameter set and annotations. The 'Pro.' note is slightly ambiguous but not a major gap.

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 and provides an example for columns. The description adds value by clarifying that names must be unique, that blanks are dropped, and that the final list must still meet the 2-item minimum after normalization. This goes beyond the schema's basic constraints.

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 and resource: 'Replace one board's columns, in order, with 2 to 12 unique names.' It also defines key constraints and behavior, so an agent can clearly tell what the tool does. No sibling tool targets column replacement, so there is no ambiguity.

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 gives clear context: use this when you need to replace a board's columns in a specific order. It does not explicitly name alternatives, but no sibling tool provides this capability, so the use case is unambiguous. The trailing 'Pro.' adds a plan/availability qualifier, though it could be more explicit.

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