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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful behavioral context not in annotations: results are ordered newest first by default, and results may carry llmContext guidance that should be followed. This meaningfully supplements the structured metadata.

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 terse sentences each add value: the first defines the primary operation and ordering, the second routes to the appropriate sibling for a specific workflow, and the third instructs on handling dynamic result guidance. No redundant wording or filler.

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?

Given the rich schema, output schema, and annotations, the description covers the essential operational behavior: listing, default order, the get_workflow alternative, and llmContext follow-up. It does not explicitly distinguish from list_workflow_runs or list_workflow_versions, but those differences are largely recoverable from tool names and schema.

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 schema fully documents all parameters and their constraints, including workspaceId/environment grants and pagination tokens. The description's 'newest first' reinforces the default sort direction implied by sortBy/sortDir, but adds little beyond what the schema already provides.

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 states a specific verb and resource: 'List the workspace's workflows.' It adds default ordering ('newest first') and explicitly distinguishes itself from get_workflow by directing users to that tool for a specific workflow's step graph. This clearly differentiates the listing tool from its main sibling.

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 provides clear usage context and names an alternative: 'Fetch a specific one's step graph with get_workflow.' It also notes to follow llmContext guidance in results. It does not explicitly contrast with list_workflow_runs or list_workflow_versions, but the core listing-vs-fetch distinction is well-covered.

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