handoff_save

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation is an upsert keyed by project+source+session_id, but omits permissions, overwrite/merge semantics, side effects, and return behavior for a mutation tool with 16 parameters.

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 sentences with no wasted words, and the operation and its intended outcome are front-loaded. It is appropriately sized for a short definition, even though it omits important details elsewhere.

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?

With 16 parameters, 0% schema description coverage, no annotations, and no output schema, two sentences cannot make the tool safely invocable. Critical parameter meanings, update semantics, and return behavior are missing.

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 0%, so the description must compensate, but it only names project, source, and session_id and gives minimal meaning ('Reuses' them as a key). The other 13 parameters, including required 'summary', are left entirely undocumented.

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 ('Create or update'), resource ('structured work checkpoint'), and intended outcome ('so another Claude/Codex session can continue from the same state'). It does not differentiate from siblings such as handoff_complete or handoff_load, so it stops short of a 5.

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 implies a use case (enabling continuation by another session) but gives no explicit when-to-use guidance, prerequisites, or alternatives to sibling tools like handoff_load, handoff_list, or handoff_complete. The reader must infer usage entirely from purpose.

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