next_task

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

With no annotations, the description carries the full burden, and it does add real value: it discloses that the acquisition is atomic and that the task payload is untrusted input from another agent. It omits lease semantics (what happens on expiry, whether claiming blocks, what the lease bounds), which is significant for a lease-based tool.

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: the operation is front-loaded and the safety warning is a deliberate, earned addition. The security caveat is slightly verbose for a warning but is not 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?

An output schema exists, so return values need no explanation, and the description covers the core action plus the security posture. For a lease-based, unannotated tool it still leaves lease behavior and its relationship to claim/release/ack unexplained.

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?

The single parameter lease_seconds has 0% schema description coverage and is never mentioned in the description, so nothing explains its units, default behavior, or expiry consequence. The description does not compensate for the schema gap.

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 take the oldest ready task addressed to this agent,' which is far more precise than the bare name next_task. It does not, however, differentiate itself from the sibling 'claim', which sounds like an alternative way to acquire a task.

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?

There is no statement of when to call this versus sibling tools such as claim, inbox, accept, or ack, nor any prerequisites (e.g., must the agent be registered?). The warning paragraph is about how to treat task content, not about when to select this tool.

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