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. The description adds real value beyond that: result ordering (most recently updated first), the fact that workflow_ids are only obtainable here, and the returned field set.

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?

Front-loads the core action, then the usage directive, then the ID-provenance rule, then the return fields — each sentence does distinct work with no 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?

An output schema exists, yet the description still names the returned fields, and it covers the ordering and the downstream workflow_id dependency. Nothing an agent needs to invoke this correctly is missing; only pagination nuance is left entirely to the 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% and both params (limit, search) are documented in the schema with usage cues like 'Raise it only if the user asked for more.' The description adds no parameter meaning beyond what the schema already carries, 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?

States a specific verb and resource ('List this workspace's workflows') plus an ordering guarantee ('most recently updated first'). This cleanly separates it from get_workflow (single fetch) and list_templates (templates, not workspace workflows).

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?

Gives clear directional guidance: 'Check here before building anything new' tells the agent when to call it, and 'Every workflow_id another tool needs comes from here; never guess one' states a hard precondition for downstream tools. It stops short of naming an explicit alternative or exclusion, so it is strong but not exhaustive.

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