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 safe-read profile is fully covered without the description. The description adds the retrieval scope ("steps and parameters") but says nothing about return format, size, or any behavioral trait beyond the annotations.

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 front-loaded sentence with zero filler; the core action is stated before the usage hint. Every word earns its place.

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 loosely signals the return ("exact steps and parameters"), which is helpful, but it leaves the workflowId parameter undocumented and does not route the agent against siblings like list_workflows or workflow_status. Adequate but with clear gaps for a 3-param getter.

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%, with deviceId and workSessionId documented in-schema, and the required workflowId (self-evidently the workflow to fetch) left undocumented. The description adds no parameter meaning at all, so it neither compensates for the gap nor exceeds the schema 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 ("Review the exact steps and parameters of a saved workflow") that clearly identifies retrieval of a stored workflow definition. It does not, however, distinguish itself from nearby siblings like list_workflows or workflow_status, leaving the agent to infer the difference.

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?

The phrase "before rerunning it" implies a usage context (pre-flight inspection prior to run_workflow), which is useful but only implied. There is no explicit when/when-not guidance or named alternative such as workflow_status for live execution state.

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