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

With no annotations provided, the description carries the full burden. It discloses what data is returned (trigger summary, step count, state, last-run timestamp) and implies a read-only operation via the verb 'List'. However, it does not mention pagination, rate limits, or return format details, which would be relevant for a list tool. The disclosure is adequate but not exhaustive.

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 two sentences with no redundancy. The first sentence front-loads the action and output fields; the second gives a concise usage context. Every word earns its place.

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 list tool with no parameters and no output schema, the description is largely complete: it states what it returns and when to use it. It lacks explicit output format (e.g., array of objects) and pagination details, but these are minor for a straightforward list operation and do not impede correct invocation.

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 tool has zero parameters, so parameter semantics are trivially satisfied. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate; the description correctly avoids adding any parameter-specific information that does not exist.

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 explicitly states the action 'List' and the resource 'the user's workflows', and enumerates the returned fields (trigger summary, step count, active/paused state, last-run timestamp). This is specific and distinct from sibling tools like workflows_get (single workflow) or workflows_runs (runs), even though they are not 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 provides clear when-to-use guidance: 'Use this to see what automations exist before creating new ones or before modifying an existing one.' It does not explicitly exclude alternative tools or name them, but the context is sufficient for an agent to know this is the discovery/list step.

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