item_claim

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior for force (immediate override, bypasses activity/stall conditions, recorded in handover history), but says nothing about failure when an item is already owned without force, permission/auth requirements, or what a successful claim returns.

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 tight sentences that front-load the core action and then qualify the option. No filler, though the semicolon clause about handover history is dense enough to skim past.

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?

A 6-parameter mutating tool with no annotations and no output schema warrants far more: only one parameter is explained, ownership-conflict behavior is implicit, and the meaning of claim_generation (likely an optimistic-concurrency token) is left entirely to guesswork.

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 0% across 6 parameters, and the description only explains 'force', including its 1–500 character constraint. agent_token, client_agent_id, claim_generation, and client_session_id are entirely undocumented anywhere, which is a significant gap for a concurrency-sensitive operation.

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 gives a specific verb and resource ('Claim an open item') plus the effect of the force option. It does not distinguish itself from close siblings such as item_takeover or item_release, so an agent still has to infer the split.

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 mention that force 'overrides existing ownership' implies when a plain claim suffices versus when force is needed, but there is no explicit when-to-use guidance and no named alternative among item_takeover/item_release.

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