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

Annotations only tell the agent this is not read-only and not destructive; the description adds real value by disclosing the claim is atomic and that the result is leased rather than permanently owned. It stops short of explaining what happens when no task is available or what occurs at lease expiry, which are the two behaviors an agent most needs to know.

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, front-loaded with the action and the selection algorithm, then the required follow-up and a documentation link. No filler, and each sentence adds a distinct piece of information.

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?

With no output schema, the description correctly compensates by naming the return value ('the leased task') and routing the agent to get_task. The notable omission is the no-work-available case and whether the lease can be extended via the renew_lease sibling, which matters for a polling loop.

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, but the description adds semantics the schema does not: worker_id determines the identity used for name-based assignment and role-matched queue lookup, and the returned task is leased under the semantics common to both parameters.

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 ('Atomically claim the next task') and goes further by spelling out the selection order: assigned-by-name work first (with or without a role), then unclaimed queued work matching the worker's roles. That detail distinguishes it from the sibling claim_task, which is presumably id-targeted.

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?

Clear context for when to call it (this is the pull-based worker loop) and an explicit next step: 'call get_task next for the full context bundle before starting work.' It does not, however, explicitly contrast itself with claim_task or list_my_tasks, so the agent must infer the boundary from sibling names alone.

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