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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds real value by specifying the depth of what is returned (full graph, node config, canvas positions, run counts) versus the summary-only sibling. It stops short of stating auth requirements or any size/rate considerations, so it is strong but not exhaustive.

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 tight sentences with no filler: the read scope comes first, then the sibling contrast, then the ordering guidance relative to update_workflow. Every sentence carries distinct decision-relevant information.

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 single-parameter read tool with an output schema and readOnlyHint already present, the description supplies everything an agent needs: what it returns, how it differs from the list tool, and when to call it in the edit sequence. Return-value details are extra credit rather than a gap.

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?

Only one parameter exists and schema description coverage is 100% ('The wf-… id.'), so the schema carries the parameter burden. The description implies the tool takes a workflow id but adds no syntax, format, or lookup guidance beyond the schema, which is the expected baseline.

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 ('Read ONE workflow') plus the exact payload scope ('the complete node/edge graph with every node's config and canvas position, plus per-node run counts'), which clearly separates it from volanea_list_resources, which 'returns summaries only.' An agent can pick this over its siblings without opening any 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 an explicit workflow: read the stored graph with this tool before editing via volanea_update_workflow, 'so you send back a modification of what is actually saved rather than a guess.' It also names the alternative (volanea_list_resources) and the condition under which it is insufficient.

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