Force-release an issue (admin)

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

Annotations already indicate destructiveHint=true. The description adds authorization context ('board_or_agent'), which is useful. However, it does not detail what 'force-release' entails (e.g., bypassing locks, consequences). No contradiction with 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 (two sentences), no fluff, and includes the REST endpoint and authorization. Could be slightly more structured but overall efficient.

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 admin action, the description lacks details on preconditions, effects, and return values. Since an output schema exists, it doesn't need to explain return values, but it should still clarify the force-release semantics. Incomplete for such a sensitive operation.

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 50%, but the description adds no extra meaning for parameters. The 'body' parameter description is generic and the 'id' in path is not explained. The description should compensate for low schema coverage but fails to do so.

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 title and description clearly state the verb and resource: 'Force-release an issue (admin)'. It distinguishes itself from sibling issue operations like pc_post_issues_by_id_release by specifying 'admin' and 'force-release'.

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?

No guidance on when to use this tool versus alternatives (e.g., pc_post_issues_by_id_release). The description only mentions authorization class but does not explain when force-release is appropriate versus other release operations.

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