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

The annotations already declare this as a destructive, non-idempotent, open-world mutation, so the safety profile is covered. The description adds useful behavioral context: status matching is lenient against the board's bug-status set and the required API scope is `feedback:bugs:write`. It does not explain reversibility or side effects beyond what annotations provide.

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 two short, front-loaded clauses with no wasted text. The core action and matching behavior come first, followed by the API scope.

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 destructive mutation with annotations and no output schema, the description covers purpose and one important behavioral trait. However, it lacks usage guidance relative to siblings and does not explain the `shortId` parameter or the expected effect of the status change.

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 50%; account and workspace are fully documented in the schema. The description adds meaning for the `status` parameter by specifying lenient name matching against the board's bug-status set, but it does not clarify `shortId` beyond its required status.

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: change a bug status by name. It also clarifies that matching is lenient against the board's bug-status set, which distinguishes it from a generic update. It does not explicitly contrast with sibling fr_set_request_status, but the bug-status wording is sufficiently clear.

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 says what the tool does but gives no guidance on when to use it versus alternatives such as fr_set_request_status. It also omits any prerequisites or conditions, aside from the API-key scope note.

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