Claim a Pickfix batch

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

With no annotations, the description carries the full burden and does well: it discloses the exclusivity constraint ('claimed only once across all sessions') and enumerates the returned payload (reviewer requests, code locations, screenshots, reference images) despite there being no output schema. It omits auth/permission requirements and what happens if a claim fails, which keeps it below 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 sentences, each earning its place: purpose and timing, returned payload, default behavior, and the once-only constraint. The action and its precondition are front-loaded before the payload detail.

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 optional-parameter tool with no annotations and no output schema, the description compensates well by describing the return contents and the exclusivity rule. The remaining gap is failure behavior (e.g., a batch already claimed by someone else) and any permission requirements.

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 100% for the single batchId parameter, so the baseline would be 3, but the description adds real semantics beyond the schema by explaining the omitted-parameter default (claims the oldest queued batch). It does not clarify format or where ids come from beyond the schema's own note.

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 and resource ('Claim a feedback batch') plus the scope of what follows (before changing code) and what the caller receives. It does not explicitly distinguish itself from siblings like pickfix_list_batches or pickfix_status, though the 'oldest queued batch' default implies the queue semantics that separate it from listing tools.

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?

'Claim a feedback batch before changing any code for it' gives an explicit precondition for use, and 'Without batchId, claims the oldest queued batch' documents the no-argument path. It stops short of naming an alternative tool or stating when not to claim, so routing between pickfix_claim_batch and pickfix_list_batches remains partly inferential.

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