Unlink an approval from an issue

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

Annotations provide destructiveHint=true, idempotentHint=true, readOnlyHint=false. The description adds that it's a DELETE operation and the authorization class 'board_or_agent', which is useful context beyond annotations. It doesn't fully clarify what 'unlink' means (e.g., does it delete the approval?), but adds value.

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 concise sentences: first states the purpose, second provides operation details. No wasted words, front-loaded.

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 simple delete/unlink operation, the description covers purpose, operation, and authorization. It doesn't mention related siblings for linking, but the core usage is clear. Output schema exists, so return format isn't needed.

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 does not explain parameters (id and approvalId) beyond their names. It doesn't compensate for the lack of schema documentation. The optional body is also unmentioned.

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 clearly states 'Unlink an approval from an issue', with a specific verb and resource. The title and HTTP method (DELETE) reinforce this. It distinguishes from siblings like pc_post_issues_by_id_approvals (link) and pc_get_issues_by_id_approvals (list).

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 does not explicitly state when to use this tool versus alternatives. It implies use for unlinking a previously linked approval, but lacks criteria or context compared to other approval-related tools.

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