delimit_handoff_create

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

Discloses side effects ('writes a new handoff receipt via ai.handoff_receipts.create_receipt') and expected follow-up (receiving agent should call delimit_handoff_acknowledge). No annotations provided, so description carries full burden. Lacks specifics on authorization or impacts on other systems, but adequate for a creation tool.

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?

Concise, well-structured with clear sections (when to use, when not, sibling contrast, side effects). Every sentence adds value; no 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?

Given 11 optional parameters, no annotations, and an output schema (not shown), the description covers usage, exclusions, side effects, and sibling distinctions well. Does not explain return values, but output schema covers that. Minor gap: no mention of default behavior when no params provided, but defaults are in schema.

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 input schema already describes each parameter. The description only mentions fields like completed/not_completed/blockers/scope in passing, adding no new semantic depth. 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 clearly states the tool's purpose: 'Create a handoff receipt when transitioning between agents.' It also explicitly distinguishes from siblings (delimit_session_handoff, delimit_soul_capture) by highlighting structural differences.

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?

Provides explicit when-to-use ('at the end of a session or before passing work to another model') and when-not-to-use ('use delimit_session_handoff for general summary, delimit_handoff_acknowledge to acknowledge'). Also contrasts with siblings via bullet points.

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