nexo_workflow_handoff

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

No annotations are provided, and the description only says 'durable' and 'honestly' without detailing side effects (e.g., overwriting, idempotency) or authorization needs. Minimal behavioral disclosure.

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?

A single 16-word sentence with no wasted words, but the brevity sacrifices substance. It is efficiently written but incomplete.

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 no output schema, no annotations, and 6 parameters with 0% description coverage, the description fails to provide enough context for correct usage. Missing details on parameter roles and expected behavior.

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%, and the description adds no meaning to any of the 6 parameters (run_id, actor, next_action, handoff_note, shared_state, new_owner). The agent gets no guidance on what these fields represent.

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 action ('Record a durable handoff') and its purpose ('so another agent or client can resume the workflow honestly'). The verb 'Record' and resource 'handoff' are specific, but it does not differentiate from sibling tools like nexo_workflow_resume.

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 usage when a handoff for resumption is needed, but it lacks explicit when-to-use or when-not-to-use guidance and does not mention alternatives among siblings.

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