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

With readOnlyHint=true already declaring the safe-read profile, the description adds genuine behavioral context: archived workflows are filtered out by default unless includeArchived is true, and it sketches the per-item payload. It does not mention pagination, ordering, or behavior when the project has none.

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 tight sentences, front-loaded with the core action and the returned fields, followed by the archiving rule. Every sentence carries information, and the field enumeration is justified because there is no output schema.

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 compensates by naming the returned fields (name, description, entry points, runnability, graph). Combined with the read annotation and archived-filter note, an agent has what it needs, with only pagination/ordering left unstated.

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%, so both projectId and includeArchived are already documented; baseline is 3. The description restates the archived-inclusion rule but adds no syntax or format detail beyond the 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?

States a specific verb (list) and resource (the project's workflows) and enumerates what each item carries. It is clearly distinguishable from get_workflow and list_projects, though it never names the singular sibling or another list alternative to route the agent explicitly.

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 natural reading is 'call this to enumerate a project's workflows,' but there is no statement of when to prefer it over get_workflow or how to find a specific workflow. The includeArchived flag is the only conditional guidance offered.

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