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

Annotations only say readOnlyHint=false and destructiveHint=false. The description adds materially valuable behavioral context: claiming locks the job against other agents, requires reading a brief and loading skills, and carries an expectation to report because an unreported job is treated as still pending. It also discloses cost and auth scope ('Free; requires the act scope'). This goes well beyond the annotations.

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 core purpose is front-loaded, and the WHEN block makes the timing highly scannable. The workflow sentence about reading the brief and doing the work is useful but slightly expands beyond the tool's own selection criteria. Overall it is purposeful and not padded.

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?

The description gives the agent everything needed to decide and act: timing, locking behavior, follow-up reporting, and auth requirements. It does not describe return values or what happens on failure, and 'brief_url' origin is unclear, but for a low-complexity claim tool this is a strong, near-complete definition.

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%, so the baseline is 3. The description does not add much beyond the schema for job_id or session_url. It references 'brief_url' as if it were a parameter, though it is not in the input schema, which slightly weakens the semantic guidance an agent can rely on.

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?

Opens with a specific verb and resource: 'Claim one queued growth move as yours.' This clearly distinguishes pick_up_job from siblings like list_queue (viewing), propose_move (creating), ship_move (completing), and skip_move (skipping). The purpose is unambiguous and actionable.

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 states when to use the tool: 'WHEN: before you start the work, never after' and explains the rationale: 'so no other agent works it too.' It also routes follow-up behavior to report_job, naming the right sibling for reporting. This is clear, contextual guidance.

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