sassy_offline_handoff

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

Beyond the annotations, the description discloses mutation, memory writes, channel mirroring, optional node launch, returned env/launch/session info, and inline errors for missing hermes_node.py or missing fallback model. This is rich behavioral context and does not contradict the 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?

The description is dense but well-organized: purpose, parameter semantics, side effects, errors, and usage. Each sentence earns its place, and the most important information is front-loaded.

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 the four-parameter tool with no schema parameter descriptions and minimal annotations, the description fully covers prerequisites, side effects, failure modes, and return values. The presence of an output schema also reduces the need to detail return shape, and the description still summarizes it.

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?

With 0% schema description coverage, the description carries the full burden and succeeds: it explains task, channel (with default 'joint'), next_steps (newline/semicolon-separated ordered steps), and start_node (launches hermes_node.py when true). Every parameter receives meaningful semantics.

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 opens with a specific verb and resource: 'Writes a structured offline handoff and optionally starts the local Hermes node.' It also names related siblings (sassy_offline_status, sassy_crosslink_recv) to place the tool in a clear workflow, so an agent can distinguish it from other sassy_* tools.

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?

Explicitly states when to use the tool: 'Use after sassy_offline_status confirms the link is down, when handing ongoing work to a local model.' It also tells the agent how to continue the workflow with sassy_crosslink_recv, providing a clear usage context.

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