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

Annotations already flag idempotentHint, destructiveHint=false, and openWorldHint. The description adds genuine context beyond them: that the call terminates the caller's active lease and that providing a recipient constrains who can accept. It does not, however, explain the failure mode of a stale lease_version (left to the schema).

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 with the primary action and the key consequence front-loaded; no filler or redundancy.

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 6-parameter mutation tool with no output schema and low schema coverage, the description covers the essential behavioral consequence but under-documents the message and task_id parameters and says nothing about what a successful handoff returns or valid checkpoint state.

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 only 33%; only lease_version and idempotency_key are documented. The description adds semantic meaning to checkpoint_id ("using a checkpoint") and to_contributor_id ("specify a recipient to restrict acceptance"), but is silent on task_id and message, so it only partially compensates for the coverage 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 (offer a task) and resource (handoff via checkpoint) and clarifies the actor relationship (to the next contributor). It is distinct from accept_handoff by naming the opposite side of the interaction, though it never explicitly references the sibling.

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?

It implies the context (offering work to a successor) and notes a key trigger (this ends your active lease), but never states when to use this versus accept_handoff or leave_checkpoint, nor any prerequisites such as holding an active lease before calling.

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