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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to repeat safety semantics. It adds useful behavioral context beyond annotations: newest-first ordering, hasMore semantics, and guidance to avoid unnecessary pagination. No contradiction exists.

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 concise sentences with no filler. Core purpose and ordering are front-loaded, the alternative get_workflow is given second, and pagination guidance is compact. The parenthetical '(workflows group)' is slightly odd but harmless.

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?

The output schema exists, so return values don't need elaboration; annotations cover the safety profile. The description covers ordering, pagination semantics, and the correct sibling for step graphs, while all six parameters are fully documented in the schema. Nothing needed for correct invocation is missing.

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 the baseline is 3 even without additional parameter detail in the description. The only added parameter context is nextPageToken guidance ('pass nextPageToken only when every item is needed') and its relationship to hasMore, which is mild extra value but not enough to raise the score.

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 clearly states the verb and resource with 'List the workspace's workflows, newest first', making the core function unambiguous. It also distinguishes itself from get_workflow by directing agents there for a specific workflow's step graph. It doesn't explicitly differentiate from list_workflow_runs or list_workflow_versions, but the resource scope and get_workflow contrast are sufficient.

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 gives explicit routing guidance: use get_workflow to fetch a specific workflow's step graph, and prefer narrow filters over pagination, only using nextPageToken when every item is needed. It doesn't cover when to choose list_workflow_versions or list_workflow_runs, but it covers the most likely alternative and the pagination decision clearly.

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