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

Beyond the readOnly/idempotent annotations, the description discloses the critical behavioral fact that no workflow steps execute and this only prepares source material, plus what the concise/detailed split drops or adds. That is exactly the kind of non-obvious context annotations cannot convey.

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 resource and its payload, and every clause carries information. There is mild overlap between the description's concise/detailed explanation and the schema's own enum description, but nothing is wasted overall.

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?

Even though an output schema exists, the description still names the notable return artifacts (diagram, builder link, handoff_check) and the no-execution guarantee, so an agent knows both what it will get and what it must do next.

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 coverage is 67% and the schema already defines response_format and revision_sha256, yet the description adds nuance: detailed is for workflows you intend to run, and the revision should be pinned to the selected one. The slug parameter is left to the schema, which is acceptable.

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 states a specific verb and resource ("Retrieve a public workflow") and enumerates what comes back: declared order, skill references, handoff_check mapping, a Mermaid diagram, and open_in_builder link. It also explicitly distinguishes itself from prepare_workflow for edits, so an agent can separate it from the other get_*/prepare_* siblings.

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?

It gives concrete routing: use prepare_workflow to change anything, use response_format=detailed before running the workflow, and pin the selected revision. It does not contrast against get_item or get_skill, but for the main branch points the conditions are explicit.

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