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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description adds no behavioral context beyond that: nothing about whether status names must be unique, what happens on duplicate name, where the status is placed in the workflow if index is omitted, or whether board_id defaults apply.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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 mutation tool with five parameters, an agent still lacks confirmation about duplicate handling, workflow placement defaults, and required permissions. The rich schema and existing annotations cover structure and safety, but the description leaves the behavioral side largely blank.

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% with 5 params, so code derivation, color format, index ordering, and board_id defaulting are all already documented in the schema. The description contributes nothing additional about parameter behavior, so the 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 ("add new statuses") and names the domain object ("board workflow"), so the agent knows this creates a status rather than listing, updating, or deleting one. It does not explicitly distinguish itself from siblings like update_status or reorder_statuses, but the create semantics are unambiguous.

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 sentence only restates the purpose ("use this command to add new statuses"); it gives no when-to-use conditions, no prerequisites (e.g., board membership/permissions), and no mention of alternatives such as using list_statuses first to avoid duplicates. The only useful hint is that statuses belong to the board workflow.

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