list_workflows

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

With no annotations, the description carries the behavioral burden. It does add useful details: this is a list/read-style operation with an optional Temporal query filter and a limit between 10 and 100. However, it omits pagination, ordering, and whether exceeding the max errors or clamps. It does not contradict any annotations.

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 purpose is stated in one front-loaded sentence, followed by a compact Args block. There is no filler, and every sentence contributes useful information.

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 simple two-parameter list tool, the description covers the core call semantics and can rely on the output schema for return values. However, it does not mention how this tool relates to the siblings and omits behavior like pagination or ordering, so an agent choosing among sibling tools may be under-informed.

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%, so the description must carry parameter meaning. It fully compensates by explaining query as a Temporal list filter with a concrete syntax example and by specifying limit's default and maximum. Both parameters receive semantic value beyond the bare 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 opens with 'List workflow executions from Temporal', which is a specific verb and resource. This clearly distinguishes it from the sibling tools describe_workflow and get_workflow_history, even though those are not explicitly named.

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 explains how to use query and limit but provides no explicit guidance about when to choose this tool over describe_workflow or get_workflow_history. There are no exclusions, prerequisites, or alternative routing hints beyond the implied meaning of 'list'.

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