List Workflows

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

The annotations (readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false) already convey that this is a safe, read-only, repeatable operation. The description's 'all' adds the scope that no filtering or parameters are applied, which is a modest behavioral detail beyond the annotations, but it does not mention pagination or return format.

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 concise sentence ('List all workflows.') that is immediately front-loaded with the action and object. There is no filler, redundancy, or unnecessary detail.

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?

For a zero-parameter, read-only, highly annotated list tool, this description is adequately complete. It clearly states the operation, and the annotations cover safety. Without an output schema, it does not spell out the return value, but for a simple 'list all' operation, the meaning is self-evident and sufficient.

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 zero properties, so there are no parameter semantics to document. The description's 'all workflows' reinforces that no arguments are needed, aligning with the 0-parameter baseline of 4.

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 'List all workflows' uses a specific verb ('List') and resource ('workflows'), with 'all' clarifying that it returns the full set rather than a single item. This distinguishes it clearly from lyzr_get_workflow (single workflow) and CRUD tools like create/update/delete.

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. It does not mention that lyzr_get_workflow is for retrieving a single workflow, nor does it discuss any filtering or prerequisites, so the agent receives no usage context.

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