session_save_handoff

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

With no annotations, the description fully discloses behavior: upsert semantics, CRDT merge, OCC, version control, disable_merge, and conversation_id verification. It clearly explains what happens on version conflict and the concurrency control mechanisms.

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?

The description is well-structured with sections for CRDT and OCC, and the main purpose is front-loaded. It is slightly verbose but every sentence adds value, making it appropriately concise for the complexity.

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?

Given 9 parameters and no output schema, the description covers the behavioral and parameter usage thoroughly. However, it does not describe the return value (e.g., success or version number), which slightly limits completeness for an upsert operation.

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 baseline is 3. The description adds value by explaining the role auto-resolution, the necessity of expected_version when a version number is known, and the effect of disable_merge. This goes beyond the schema's basic descriptions.

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 clearly states 'Upsert the latest project handoff state for the next session to consume on boot,' specifying the verb, resource, and context. It distinguishes from sibling tools like session_load_context by focusing on saving state.

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 explicitly mentions when to use (after a session to save context for next boot) and provides conditions for expected_version. However, it does not explicitly mention when not to use or list alternative tools, which would raise it to a 5.

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