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 without the description. The one genuinely additive line is that request schemas must be fetched via describe_tool / the operation ID (94bb04fb...), which tells the agent the input contract is not self-documenting here. Nothing contradicts 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?

The description is short but wastes its entire first half on a verbatim duplicate of the same path string, which earns nothing. The remaining clause is a useful pointer but is buried behind the repetition.

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?

For a read-by-ID endpoint with no output schema, the description should tell the agent what the returned workflow object represents and what happens on an unknown ID. It supplies neither, leaving the agent to discover everything through describe_operation.

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% for 2 parameters, one of which (params.id) is required, so the description must compensate and does not. The ':id' in the path weakly implies the required identifier, but there is no explanation of what kind of ID it is, its format, or the optional 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 the endpoint path repeated twice, which merely restates the tool name/title ('automation-workflows: GET /api/automation-workflows/:id'). It never says in plain language what the resource is, what a workflow contains, or what the agent gets back. It does implicitly distinguish the by-ID fetch from the list sibling, but only through the same path string the name already provides.

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 call this versus the sibling list tool (get_automation-workflows_), the instances endpoints, or describe_operation. The single pointer to 'describe_tool provides native request schemas' hints at a workflow but not a usage condition.

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