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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavioral detail beyond that: the item leaves the pending list and a QUEUE_ITEM_COMPLETED webhook is sent, and it frames the operation as a dashboard check-off. It does not cover permissions or error behavior, so it is not a 5.

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?

Three short sentences, front-loaded with the core action and followed by useful behavioral and alternative-tool context. No sentence is redundant.

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 mutation with annotations covering safety traits, the description supplies the important effect and side effect plus a clear alternative path. It does not address error cases or permission requirements, but no output schema exists and the remaining gap is minor.

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, including id, itemId, or the project-scoping rules for projectId. The schema itself carries the parameter meanings for the nested request fields, so the schema is doing the heavy lifting and the description adds no parameter-level value.

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 states a specific verb and resource (resolve a queue item) and defines the effect clearly: the item leaves the pending list. It does not explicitly distinguish itself from siblings such as queue-items-unresolve or queue-items-resolve-many, so it falls short of a 5.

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?

It establishes when to use the tool as the equivalent of checking off an item in the dashboard, and it points the agent to POST /actions/execute when a moderation action is also needed. It does not explicitly say when to choose this over queue-items-unresolve, but the usage context is clear.

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