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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the returned payload in detail — ordered steps with app/action, run inputs, deployment, schedules, estimated cost, dashboard link — which is important because no output schema exists.

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 the scope front-loaded and no filler. The colon-separated list is dense but each item conveys distinct returned content; the only slight cost is that the list-heavy phrasing reads more like a payload manifest than a purpose statement.

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 one-parameter read tool with no output schema, the description carries the return-value burden well and the annotations cover safety. Remaining gaps are minor: no mention of behavior for an unknown id, size limits for large workflows, or whether cost is static or a live estimate.

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 100% for the single workflow_id parameter, and the schema itself explains where the id comes from. The description adds no further meaning about the identifier or its format, so the schema does all the work; baseline 3 is appropriate.

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?

"One workflow in full" names a specific resource and scope, and the enumeration of contents (steps in order, inputs, deployment, schedules, cost, dashboard link) makes the retrieval concrete. It is a content description rather than a verb phrase, but an agent can distinguish it from list/search siblings by the 'one ... in full' framing.

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 explicit when-to-use or when-not clause, and no sibling is named as an alternative. Usage is only implied: 'one workflow in full' signals a single-item detail fetch, and the required workflow_id signals it is for a known workflow. The prerequisite hints (search_workflows, use_template) live in the schema, not the description.

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