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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description usefully adds the observable effect ('the item comes back in the pending list'), but says nothing about permission requirements, what happens to resolution metadata (who resolved it, when), or the error raised when unresolving an already-pending item. With annotations present the bar is lower, so a 3 fits.

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 short sentences: the effect is front-loaded, then an analogy that removes ambiguity. No filler or redundancy.

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 single-object mutation with no output schema, the definition conveys what happens to the item and that it is an undo of a resolve. It leaves gaps around error cases, permission level needed, and whether the item's prior resolution data is preserved — relevant for a non-idempotent mutation.

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 top-level `request` object has 0% schema description coverage, and the description never names or explains any parameter — it only implies a queue and an item must be identified. The subtle projectId scoping rule ('required with an organization key unless the key reaches only one project') lives only in the nested schema and is not reinforced here.

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?

States a specific verb (unresolve) and resource (queue item) and immediately clarifies the semantics with 'Mark a resolved item of a queue as pending again.' This clearly separates it from siblings queue-items-resolve and queue-items-resolve-many.

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 dashboard analogy ('same as removing a check-off') gives an unambiguous usage context and preconditions: the item must currently be resolved. It does not explicitly name the inverse sibling (queue-items-resolve) or state what happens if the item is already pending, so it stops short of full routing guidance.

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