nexo_workflow_list

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

No annotations provided, so description bears full burden. Only states it lists runs; no disclosure of side effects, permissions, rate limits, or pagination behavior. Minimal behavioral transparency.

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?

Single sentence, front-loaded with verb and resource, no wasted words. Efficient and clear.

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?

Despite having 3 optional parameters and no output schema, description barely covers core purpose. Missing details on status values, limit behavior, and output format. Would benefit from examples or parameter hints.

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 descriptions coverage is 0% and parameters are not explained in description. 'status' is hinted by 'active, blocked, and resumable' but not explicitly clarified. No mention of 'include_closed' or 'limit' meaning.

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?

Description clearly states action 'List durable workflow runs' and purpose 'so active, blocked, and resumable work stays visible'. Distinguishes from sibling tools like get, open, run by specifying it's a listing 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?

Implied usage for visibility of certain workflow states, but no explicit when-to-use or when-not-to-use guidance. No mention of alternatives like get for single workflow or run to start.

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