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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds useful context by stating that each entry carries its latest published version and draft revision. It says nothing about pagination, result limits, or ordering, which matters for a list operation.

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?

It is a single well-formed sentence with no wasted words, and the resource and returned content are front-loaded. It is lean to the point of omitting any routing or behavioral cues, but nothing present is redundant.

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, the description usefully names the returned fields, and annotations cover the read-only nature. However, for a list tool it omits whether results are paginated or filtered by default when query is absent, leaving a real gap for 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?

Schema description coverage is 100%, and the single optional query parameter is fully documented in the schema as "Words to search workflow names for." The description adds no further meaning, such as how matching behaves or that omitting query returns everything, so the baseline of 3 applies.

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 gives a specific verb and resource ("Lists the workspace's workflows") and adds the scope of returned data (latest published version and draft revision). It is clear on its own, but it never mentions how it differs from the sibling get_workflow, which retrieves a single workflow.

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 guidance on when to use this versus get_workflow or list_runs, and no stated prerequisites or exclusions. An agent must infer that this is the enumeration path from the name and the phrase "the workspace's workflows" alone.

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