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

Annotations declare destructiveHint=true, which could read as data loss; the description usefully clarifies that archiving only hides the board from search and my-tasks 'without deleting anything.' That reframes the destructive flag and is real added value, though it doesn't cover permissions or unarchive behavior (which the schema supplies).

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 tight sentences: the operations first, then the one non-obvious consequence. No filler, and the most decision-relevant detail (archiving) is not buried.

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 annotations present but no output schema, the description covers what changes and the soft-delete semantics. It omits any authorization/permission note and does not mention that unarchiving is possible, a minor gap given the schema covers the field.

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 goes beyond the schema by explaining the *effect* of the archived parameter rather than just restating it. Name/description/icon/colour are covered equally well by the schema.

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 (rename/change/archive) against a specific resource (board) and enumerates the updatable fields. The 'board' scope cleanly separates it from the sibling update_kanban_card and update_kanban_column tools.

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?

Usage is implied by the enumerated field operations, and the archiving sentence explains a consequence, but there is no explicit when-to-use guidance or stated alternative (e.g., delete_kanban_project vs archiving). The agent must infer the choice itself.

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