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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of what a missing/invalid id returns, whether the instance payload is large, or any scoping rules.

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?

The same route sentence is duplicated back to back, which is pure waste, and the front-loaded content is a URL rather than a human-readable purpose. It is short but not economical or well-structured.

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, a nested free-form `query` parameter, 0% schema description coverage, and no explanation of the returned instance shape, the description leaves nearly everything an agent needs unanswered. The tool name in sibling list is also nearly identical to a list endpoint, making disambiguation essential and absent here.

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 0% across both the nested `query` object and `params.id`. The path template `:id` weakly signals that `id` identifies the instance, but the description gives no format, source, or meaning for it and says nothing about the free-form `query` object.

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 is a verbatim restatement of the tool's HTTP route and title, repeated twice, plus an operation ID. A reader can infer it fetches one automation workflow instance by id, but the description itself never says so in plain language or distinguishes it from sibling get_automation_workflows_instances_9e577d22f7b78a9d70fdac4e (the list variant).

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 statement of when to use this endpoint versus the instances list, the workflow-by-id endpoint, or describe_operation. The only actionable pointer is that describe_operation holds the native request schemas, which is a schema hint rather than usage guidance.

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