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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value by disclosing that archived workflows are included in results and summarizing the fields each item returns, which helps the agent decide whether the listing is sufficient without a follow-up call.

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-loaded with the subject and scope, then the sibling disambiguation, then the display rule. Every sentence carries information, though the UUID-display guidance is generic output hygiene that sits slightly apart from the tool's purpose.

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?

For a zero-parameter list tool with an output schema and full annotation coverage, nothing an agent needs to call it correctly is missing: scope, contents, the sibling alternative and output formatting are all stated.

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, so there is nothing for the description to disambiguate; baseline applies. The formatting instruction about presenting names and locales rather than UUIDs is a useful constraint on how the agent handles the output, adding value 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 and resource (lists the organisation's Workflows) plus scope (archived ones included) and enumerates what each entry carries: reads, target languages, current version, latest run. It explicitly differentiates from the sibling get_workflow, which returns a single workflow with its definition.

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?

Names the alternative and the distinguishing condition — use get_workflow when the full definition of one workflow is needed, otherwise list. It gives no explicit when-not-to-use or scoping caveats beyond 'archived ones included', so it stops short of a full routing rule.

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