nexo_workflow_open

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

No annotations are present, so the description must carry the burden. It mentions 'durable workflow run' implying persistence, but does not disclose side effects, permissions, idempotency requirements, or behavior on duplicate attempts.

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 but lacking structure. It trades completeness for brevity, missing key information needed for correct invocation.

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 tool's complexity (11 parameters, durable workflow concept) and lack of output schema, the description is insufficient. It does not convey return values, workflow lifecycle, or how to handle the opened workflow.

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 does not explain any of the 11 parameters (e.g., sid, goal, goal_id, workflow_kind). The agent has no context for parameter meanings or defaults.

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 it opens a durable workflow run for long multi-step or cross-session work. It distinguishes from siblings like nexo_workflow_get, nexo_workflow_list, and nexo_workflow_update, but does not explicitly differentiate from nexo_workflow_resume or nexo_run_workflow.

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 vs alternatives (e.g., nexo_run_workflow, nexo_workflow_resume). There are no prerequisites, context for use, or exclusions mentioned.

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