Hand off work item

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

Annotations only indicate a non-read-only, non-idempotent, non-destructive operation. The description adds meaningful behavioral context: the transfer is restricted to the current holder and the receiving session must use resume to pick up the item. This workflow coupling is not present in the structured annotations.

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 concise sentences that front-load the primary action, then give the key constraint and the sibling relationship. No filler or repetition. Every sentence contributes useful 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 simple 2-parameter tool with no output schema, the description covers the operation, the authorization constraint, and the follow-up workflow (resume). It omits possible error behavior, but this is a minor gap for such a straightforward transfer action.

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 parameter meanings are fully documented in the input schema. The description references 'session token' in line with the schema's 'new owner session token' but does not add further semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific action ('Transfer ownership') and resource ('progress work item') to a specific target ('another session token'), and further clarifies the scope with 'only the current holder can'. It also explicitly contrasts with the sibling tool 'resume', making it easy for an agent to distinguish handoff from the receiving-side operation.

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 description gives clear usage context: use handoff to transfer ownership and resume to pick it up on the receiving side. It also notes a key prerequisite ('only the current holder can'). It does not, however, enumerate explicit when-not-to-use conditions beyond the holder constraint, which is a minor gap.

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