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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful behavioral detail that results are limited to workflows owned by the authenticated profile, i.e. no cross-account visibility. It says nothing about ordering, pagination, or completeness of the list, which would be valuable for an enumeration tool.

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?

A single sentence with no filler, and the ownership qualifier is placed where it matters. Nothing could be removed without losing meaning.

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?

With zero parameters, full annotation coverage and an output schema that documents the return shape, the description needs only to state scope and does so. The remaining gap is minor: it does not mention whether the list is paginated or ordered, which an agent gathering many workflows might want to know.

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 beyond what the empty schema already conveys. The baseline for a parameterless tool applies, and the ownership statement usefully explains what the implicit filter is.

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 uses a specific verb and resource ('Lists all workflows') and scopes the result set to those 'owned by the authenticated profile', which distinguishes it from a generic resource fetch. It does not explicitly contrast with sibling tools like get_workflow or create_workflow, so differentiation is only implicit in the word 'all'.

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?

Usage is implied rather than stated: 'Lists all workflows' suggests enumeration is the right call when the agent needs the full collection, and the ownership scoping hints at what will and won't appear. There is no explicit when-to-use guidance, no mention of when to prefer get_workflow for a single item, and no stated prerequisites.

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