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

Adds substantial context beyond annotations: the 15-minute TTL, auto-assignment of unassigned items to the caller, return payload (claim_token, new version, assignee), renewal-vs-new-claim semantics, and the two distinct conflict outcomes (conflict_claimed vs conflict_stale) with remediation for the latter.

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?

A single front-loaded block that leads with the action and lease duration, then parameters, returns, and error codes in priority order. No filler; semicolons keep it dense without losing parseability.

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?

Covers the mutation's safety profile, concurrency semantics, the value needed for downstream submit_resolution, and failure modes. With an output schema present it doesn't need to over-detail the return shape, which it correctly only summarizes.

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 coverage is already 100%, so the baseline is 3. The description earns above baseline by explaining the interplay the schema states only in isolation: expected_revision/expected_version must be what you read, and claim_token switches the call from claim to renew.

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 (claims), resource (an open item), and explicit state transition (open → in_progress) with a 15-minute lease. An agent can distinguish this from release_feedback and submit_resolution without opening any schema.

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?

Explicitly frames the when: before working on an item, to prevent concurrent work, and notes the renewal path via claim_token. It does not name release_feedback as the cleanup step after finishing, so the alternative-routing is clear for use but not for release.

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