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 covered by structured data. The description adds useful behavioral context by describing the returned payload, but says nothing about failure modes such as an unknown or inactive workflow_id. Against an already-annotated read tool, this is adequate rather than rich.

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?

Two sentences, both earning their place: the first defines the output, the second defines the calling context. The payload description is front-loaded ahead of the sequencing advice, with no filler.

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 no output schema, the description carries the burden of explaining return values and does so reasonably (field list, types, required flags, option sets). For a single-param read tool this is nearly complete; only error behavior for invalid IDs is unaddressed.

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?

There is a single required parameter at 100% schema description coverage, so the schema fully documents workflow_id. The description adds no additional meaning such as accepted ID ranges or where to obtain a valid ID. Baseline 3 is appropriate when the schema does the work.

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 gives a specific verb and resource ('Return one workflow's full field list') and enumerates the payload contents (types, required flags, option sets), so an agent knows exactly what comes back. It does not distinguish itself from near-siblings like describe_workflow or describe_workflow_template, which is the main gap.

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 states a concrete usage rule with a named sibling: call this before submit_request to learn mandatory values and formatting. That is clear when-to-use guidance rather than implied. It stops short of explicit when-not-to-use guidance or a comparison with describe_workflow/describe_workflow_template.

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