resolve_pull_request_review_thread

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds value beyond these by noting that the tool verifies repository/PR/state/permission before acting, and that repeating an already-resolved request is a no-op — which reinforces and elaborates on the idempotentHint. This adds behavioral context about verification steps and idempotent behavior that annotations alone don't convey.

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 that front-load the primary purpose and add a valuable idempotency note. Zero wasted words, no redundancy with the schema or annotations.

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 state-changing action with no output schema, the description covers the key points: what it does, preconditions (verification steps), and idempotent behavior on repeat. It's a relatively simple tool with 5 parameters (no nested objects). The main gap is lack of parameter format guidance for reviewThreadId, but overall this is quite complete for the tool's complexity.

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% (only the repository parameter has a description). The tool description adds no parameter-specific detail beyond what's in the schema — it doesn't explain formats for reviewThreadId, pullRequestNumber, account, or hostname. With low coverage, the description could have compensated but doesn't. Baseline 3 applies since the schema has minimal descriptions.

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 verb (resolve) and resource (review thread), and specifies the context (pull request, repository). It distinguishes from siblings like unresolve_pull_request_review_thread by using the 'Resolve' verb. However, it doesn't explicitly differentiate it from other review-thread tools beyond the verb itself.

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 mentions verifying repository, pull request, current state, and viewer permission before resolving, which implies preconditions. But it doesn't explicitly state when to use vs not use this tool versus the sibling unresolve_pull_request_review_thread, other than the implied inverse relationship. No explicit statement of when NOT to use it.

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