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

The annotations only declare non-read-only and non-destructive, so the description carries the burden of explaining side effects. It does this well by stating that claiming reserves the job, that reporting is required, that it is free, and that it requires the 'act' scope. It does not cover failure cases or idempotency, but the core behavioral profile is clear.

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?

The description is front-loaded with the core action, then the timing constraint, then the workflow. It is slightly dense as one paragraph, but every sentence earns its place and there is no redundant filler.

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 state-changing claim tool with no output schema, the description gives the essential context: what to do before and after calling, why reporting matters, the required scope, and cost. It does not describe the return value or duplicate-claim behavior, but those are minor gaps given the actionable guidance provided.

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 100%, so parameters are already fully documented: job_id is a uuid from list_queue, and session_url lets the founder open the session. The description does not add significant meaning beyond the schema, though it does reference brief_url as something to read after claiming, which is context rather than a parameter.

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 one queued growth move as yours.' This clearly distinguishes pick_up_job from sibling tools like list_queue (listing), propose_move (proposing), ship_move (finishing), and skip_move (skipping). The added WHEN condition further disambiguates it from post-work 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?

Explicitly says when to use it: 'before you start the work, never after,' and explains the rationale: 'so no other agent works it too.' It also directs the agent to read the brief, load skills, do the work, and report via report_job, giving a clear end-to-end usage path.

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