list_workflows

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

No annotations are provided, so the description carries the burden. It adds useful context about workflow bindings and lifecycle events, but does not disclose potential side effects, authentication requirements, or response format details. Since this is a read-only listing, the lack of danger may be acceptable, but the description could be more explicit.

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?

Two concise sentences: the first states what the tool does, the second gives the usage rationale. No wasted words or redundant information, and the key action is front-loaded.

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 simplicity (2 optional params, no output schema), the description covers the main purpose and includes practical context about workflow bindings. It lacks an explicit statement of what the response contains (e.g., workflow names, IDs), but the schema and straightforward nature make this a minor gap.

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 100%, so the baseline is 3. The description mentions 'optionally with their event bindings' but does not elaborate on the limit or entityFilter parameters, relying on the schema for their meaning. It adds little beyond schema.

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 uses a specific verb ('List') with a clear resource ('all workflow definitions in the system') and adds scope ('optionally with their event bindings'). It distinguishes itself from sibling tools like get_workflow (single workflow) and execute_workflow (executes, not lists).

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?

Provides a clear use case: 'Use this to understand what business logic runs when data changes.' This tells the agent when to invoke the tool, though it does not explicitly mention alternatives or when not to use it. The context is enough for most selection scenarios.

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