list_workflow_instances

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

No annotations are provided, so the description carries the full burden of disclosure. 'List' weakly implies a read-only operation, but the description does not mention pagination, result limits, ordering, filtering, or what happens when no instances exist. This is insufficient for a list endpoint with no annotation safety signals.

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, front-loaded sentence with no filler or redundancy. It is terse, but given the small parameter surface, it does not waste the agent's attention. It simply lacks benefit beyond being short.

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?

There is no output schema, so the description should help the agent understand what the response contains or how the listing behaves. It does neither, and it omits pagination and filtering behavior that matter for a list operation. The low parameter count helps, but important contextual information is still missing.

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?

The input schema has 100% description coverage, with account_id and workflow_name both having clear descriptions. The tool description itself adds no parameter-level meaning beyond the schema, but the schema already documents the two required parameters adequately, so the baseline of 3 applies.

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 a specific verb ('List') and a specific resource ('instances of a Workers Workflow'), so the core action is clear. It does not explicitly distinguish itself from sibling tools like list_workflows or get_workflow_instance, but the resource phrasing is specific enough to infer the difference.

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 gives no guidance on when to use this tool versus alternatives such as get_workflow_instance or list_workflows. There is no mention of prerequisites, exclusions, or context that would help an agent decide between this and similar listing tools.

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