Next task

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false), and the description adds real value on top: the 30-minute abandonment/retry rule is a non-obvious behavioral trait an agent could not get from structured fields. It does not cover failure behavior when no pending task exists, which keeps it below 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?

Two tight sentences, zero filler, with the core action front-loaded and the exception rule second. Nothing could be removed without losing 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?

For a non-idempotent claim operation with no output schema, the description should say what comes back (task fields? an ID for later complete_task?) and what happens when the queue is empty. Neither is covered, leaving a meaningful gap for an agent wiring this into a workflow.

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% and the single task_group parameter already carries its own description ('Defaults to the latest group'). The tool description adds no additional semantics about what a group is or how selection interacts with the default, so the baseline 3 applies.

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 the next pending task and mark it running' — which clearly distinguishes it from siblings like get_task_status (read status) and complete_task (finish work). It stops short of explicitly naming those siblings, so it doesn't reach the top band.

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 claim-based verb implies the worker-pickup use case, but the description never states when to use this versus get_task_status or complete_task, nor any preconditions (e.g., must a task group exist first). Usage is inferable but not guided.

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