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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: exactly which fields each entry carries and, importantly, that the input_schema reflects what create_run expects — information not present in annotations or the (empty) input schema.

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?

Two sentences, front-loaded with the core action and scope, with no filler. The second sentence is dense but the parenthetical definitions of input_schema/output_schema earn their space by tying the output to create_run's contract.

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 must describe return values — and it does, enumerating the entry fields and the optionality of description/schemas. Minor gaps remain (ordering, whether all workflows are always returned, empty-list behavior), but for a zero-parameter read-only list tool this is sufficient to call correctly.

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?

The tool takes zero parameters, which sets a baseline of 4. The description goes slightly further by documenting the fields of each returned entry (name, description, input_schema, output_schema) and what those schemas mean in practice, though with no parameters there is nothing else to disambiguate.

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 the organization's saved workflows") and immediately clarifies the domain term with a parenthetical ("reusable run definitions"). It also distinguishes the tool's output from an execution tool by pointing to create_run, so an agent can tell it apart from get_workflow and create_run without opening a schema.

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 a clear usage context: use this to discover workflows and their schemas "so you can call a workflow without reading its prompt," then run one with create_run by name. It stops short of naming when to prefer get_workflow for a single workflow or when listing is unnecessary, so it is clear context without explicit exclusions.

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