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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only that the response includes the graph and an inbound trigger URL. It does not say whether the call is read-only, what happens for a nonexistent or deleted workflow, whether the graph is large or paginated, or whether permissions are required.

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 tight sentence with no filler, and the most useful fact (the full graph) is front-loaded. The telegraphic 'incl.' phrasing reads more like a changelog note than a complete sentence, but it wastes nothing.

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 one parameter, no output schema, and no annotations, the tool is simple enough that a short description can suffice, and noting the returned graph and trigger URL is genuinely helpful. Still missing is any statement of read-only nature or how the ID is obtained.

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 0% for the single parameter workflow_id, so the description must compensate and it does not. Nothing explains the ID's format, source, or whether it accepts names, slugs, or deleted-workflow IDs.

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 names the resource (workflow) and enumerates what the payload contains (graph nodes/edges, inbound trigger URL), which implies a full-detail retrieval. However, it never states a verb such as 'retrieve' or 'fetch', and it does nothing to separate itself from sibling workflow_list or workflow_history_get.

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?

There is no guidance on when to call this rather than workflow_list (which presumably returns summaries) or workflow_history_get. No prerequisites, no exclusions, no mention of the required workflow_id originating from a list call.

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