handoff_session

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

With no annotations, the description covers key behaviors: building a markdown brief, saving to ~/.agent-bus/handoffs/, and conditional seeding. It does not detail side effects (e.g., file persistence) or authorization needs.

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: first states purpose, second explains mechanics. Front-loaded with the verb and resource, no filler. Every word adds value.

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?

No output schema, 7 parameters, moderate complexity. The description covers the workflow but does not describe return values (e.g., format of commands) or what happens on failure. Adequate but incomplete for full agent guidance.

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 57%. The description adds context only for the launch parameter (false returns command, true seeds session). Other parameters like from_agent, to_agent, session_id, instructions are not elaborated, leaving the agent to infer meaning from schema alone.

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: 'Hand a session's context from one agent to another.' It specifies the actions (builds a markdown brief, saves it, returns command) and distinguishes from siblings like read_session.

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 explains the two modes via the launch parameter (return command vs. seed session). It implies when to use this tool (for handoffs), but lacks explicit instructions on when not to use it or alternatives like read_session.

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