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

No annotations are supplied, so the description carries the full burden. It partly compensates by disclosing the exact fields returned (id, name, enabled, cron_expr, graph, inbound_trigger_url, last_run), but omits whether results are paginated, ordered, filtered by ownership, or truncated for large accounts.

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?

A single front-loaded sentence: the action first, then the returned fields in a compact parenthetical. Nothing is wasted and nothing is buried.

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?

With no output schema and no annotations, the field list is the key missing piece and the description supplies it. It falls slightly short on listing scope (pagination, ownership, ordering) for a tool that could return many records.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The field enumeration in the description is a bonus that relates to the response, not the input.

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 names a specific verb and resource ('List your workflows') and enumerates the returned fields, so the agent knows exactly what comes back. It does not explicitly differentiate itself from close siblings such as workflow_deleted_list or workflow_runs_list, leaving scope boundaries to inference from 'your workflows'.

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?

There is no statement of when to use this tool versus workflow_get, workflow_deleted_list, workflow_history_list, or workflow_runs_list. The only guidance is the implied 'list = browse', which an agent must infer on its own.

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