Un-archive issue from inbox

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

The annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the authorization class 'board_or_agent' and the HTTP method, which provides additional behavioral context beyond the annotations. No contradiction.

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 concise with two short sentences that directly convey the purpose and the HTTP method/auth class. No unnecessary information.

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?

Given the tool has 2 required parameters with zero schema descriptions and an output schema exists, the description is incomplete as it does not explain parameters or return value. The tool is not self-contained for an agent to invoke correctly without guessing parameter meanings.

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?

The description does not mention any parameters. The input schema has two required parameters (path.id and body.userId) with no descriptions, and the description fails to explain their meanings or usage. Schema coverage is 0%, so the description should compensate but does not.

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 the action 'Un-archive issue from inbox', which is a specific verb and resource. The title and HTTP DELETE method distinguish it from the archive counterpart (pc_post_issues_by_id_inbox_archive). However, the description does not explicitly differentiate from siblings.

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 provides no guidance on when to use this tool versus alternatives. It lacks any mention of conditions, prerequisites, or scenarios where this tool is appropriate. The sibling list is extensive but no direction given.

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