nexo_workflow_handoff

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'durable', implying persistence, but fails to mention side effects, ownership requirements, or whether the handoff is appended or overwrites. The minimal description leaves significant behavioral traits undisclosed.

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 a single sentence, concise and front-loaded. However, its brevity sacrifices informativeness; it could be expanded slightly to cover key details without losing conciseness.

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 lack of output schema and the tool's moderate complexity (6 parameters), the description is incomplete. It does not explain the return value, success conditions, or how a handoff differs from other workflow operations. An agent would need additional domain knowledge to use it correctly.

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 0%, and the description adds no information about the six parameters (run_id, actor, new_owner, next_action, handoff_note, shared_state). The agent receives no semantic guidance beyond the parameter names, which are insufficient for correct invocation.

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 states the verb 'Record' and the resource 'workflow handoff', making the purpose clear. Among sibling tools, it is unique as the only handoff-related tool, distinguishing it effectively. However, it does not explain what a workflow handoff entails, leaving some ambiguity about the exact operation.

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?

No guidance is provided on when to use this tool versus alternatives like nexo_workflow_update, nexo_workflow_resume, or nexo_workflow_compensation. The description lacks context on the appropriate scenarios for a workflow handoff, making it hard for an agent to decide when to invoke this tool.

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