unresolve_pull_request_review_thread

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds the idempotency detail independently ('Repeating an unresolved request is a no-op'), aligning with idempotentHint. It also discloses the internal verification steps (repository, PR, state, permission), which is useful 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?

Two informative sentences with zero waste. The description is efficiently front-loaded with the primary action first, then the no-op behavior clarification. Slightly more compact than ideal given the parameter documentation gap it leaves uncovered.

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?

With no output schema and only 20% schema description coverage, the description should provide more. It covers the action and idempotency well but leaves the 'account' and 'hostname' parameters unexplained, and doesn't describe what the response looks like. For a state-transition tool this is adequate but not complete.

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 only 20%, so the description carries significant burden for explaining parameters beyond 'repository' which has a format note. The description names the resource identifiers (repository, pullRequestNumber, reviewThreadId, account) but doesn't explain what 'account' means, hostname's role, or add syntax/format details beyond the schema patterns. With 5 params and 20% coverage, this is a notable gap.

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 verb+resource is specific ('Reopen a resolved review thread') and the description clarifies the state transition. However, it doesn't explicitly distinguish from its sibling 'resolve_pull_request_review_thread' by name, though the semantic reversal is clear from context.

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 implies it operates on a resolved thread (to reopen it) and mentions prerequisites (verify repository, pull request, current state, viewer permission). It doesn't explicitly name when NOT to use it or reference alternative tools, but mentions the no-op behavior for repeated unresolved requests which is useful edge-case guidance.

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