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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: archived workflows are omitted by default and only surfaced when includeArchived is true, and it lists the entry-point types. It stops short of mentioning pagination or result size, which would be the remaining gap.

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?

Three short sentences, front-loaded with the action and result shape, then the scoping rule. The middle sentence about a project having several workflows is slightly filler but still earns its place by clarifying the plural result.

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?

There is no output schema, so the description carries the burden of describing return contents and does so by enumerating the per-workflow fields. Combined with the archived-filter rule, an agent has enough to call this correctly; only pagination/ordering details are absent.

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 coverage is 100%, so the schema already documents both projectId and includeArchived, setting the baseline at 3. The description restates includeArchived's effect but adds no format, default, or interaction detail beyond the schema text.

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 a specific verb+resource ('List the project's workflows') and scopes it to a project, which distinguishes it cleanly from the singular sibling get_workflow. It even enumerates the fields returned (name, description, entry points, runnability, graph), so an agent knows exactly what it gets.

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?

Usage is only implied: the plural 'list' versus the sibling get_workflow's singular fetch is left for the agent to infer. The one explicit routing rule is the includeArchived behavior, which is useful but narrow; there is no stated when-to-use/when-not guidance relative to list_projects or get_workflow.

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