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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing real side effects an agent could not see in the schema – date stamping on transition and, on release, drafting the changelog post plus linking both ways. It does not address permissions, failure behavior, or what publish=true does beyond staging.

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 sentences, front-loaded with the action and its central side effects, then a terse prohibition. The parenthetical compresses several behaviors without fluff; nothing is redundant with the name or 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?

For a 9-parameter mutation with no output schema, the description covers the non-obvious behaviors (auto-stamped dates, changelog drafting/linking, derived fields to avoid) that an agent cannot recover from structured fields. What is missing is modest: the effect of publish, archived-state/`reply` handling, and return information.

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; the description earns a bump by explaining why `at` exists (backfilling the status stamp) and why `draftChangelog` defaults true (board defines a changelog collection), plus the do-not-set guidance for derived fields. Undocumented in the description: `reply`, `publish`, and `context` semantics beyond what the schema already says.

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+resource ("Change a roadmap/board item status") and enumerates the consequences (date stamping, changelog drafting, bidirectional linking), which separates it from generic content mutators like patch_content. It never names a sibling it is not, so differentiation is inferential rather than explicit.

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 parenthetical defines the situation in which to call it (status transitions that need date stamps and/or release changelog drafting), and "Never hand-edit *At, daysToRelease, or votes" gives an explicit when-not with the implied redirect (use this tool rather than a field-level patcher). No sibling tool is named, so the agent must still infer which alternative to pick for those fields.

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