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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context of its own and leaves an important ambiguity: whether 'filtered by node type' narrows the returned workflow structure or changes which automation is matched. No permission or rate-limit notes.

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 compact sentence with no filler, front-loaded with the core action. It is efficient, though the brevity leaves the node_type ambiguity unaddressed.

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 should indicate what 'details' means (workflow structure, nodes, status, metadata), and it does not. For a simple two-parameter read tool this is a moderate gap rather than a fatal one, since the annotations cover safety.

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% (both parameters documented), so the baseline is 3. The description restates 'optionally filtered by node type' but does not clarify what filtering means here - whether it returns only nodes of that type within the workflow or affects matching - which is exactly the detail the terse schema description lacks.

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 ('Get details of a specific automation workflow'), which is unambiguous. There are no other automation-related siblings in the list, so differentiation is less of a concern, but it does not distinguish itself with respect to the many other 'get_*' tools.

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?

Usage is only implied: the agent can infer it is for fetching a known automation by ID plus an optional filter. There is no explicit when-to-use guidance, no preconditions, and no mention of alternatives or what to do when the ID is unknown.

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