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

Annotations only declare that this is not read-only, not idempotent and not destructive; the description goes further by disclosing the lease model, the 60-minute default, the 5-1440 bound, and that re-calling renews rather than duplicates. It leaves unstated what happens on conflict (already claimed) or whether a lease must be explicitly released, which matters for a non-idempotent mutation.

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 short sentences with no filler: purpose and effect first, renewal rule second. Every clause carries information that is not duplicated by the name, title or schema.

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 four-parameter, fully schema-documented, no-output-schema tool, this covers what an agent needs to make the call and to keep the lease alive. The remaining gap is response behavior on contention and whether a lease can be released before expiry, which the description does not address.

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 the baseline is 3, but the description adds genuine meaning the schema lacks: the default lease length of 60 minutes and the permitted 5-1440 range for the 'minutes' parameter that the schema only labels 'Lease length'. It adds nothing for ref, note or allowTerms, but those are already documented in the schema.

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?

The description names a concrete verb and resource ('Take a task or issue') and, more importantly, states the effect that distinguishes it from the rest of the catalog: it acquires a lease 'so other agents leave it alone'. The renewal sentence makes the claim/renew pairing explicit against the obvious counterpart, release_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?

'Renew by claiming again' is explicit operational guidance for the recurring case, and the exclusivity rationale tells the agent why to reach for this tool. It stops short of stating when not to use it (e.g. what to do if the task is already held by another agent).

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