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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds nothing beyond those hints and the describe_operation pointer — no pagination behavior, response shape, or filtering semantics for a collection endpoint.

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?

It is short, but the brevity comes from duplication, not density: the same path string is printed twice and the operation ID adds no decision value. Nothing is front-loaded about behavior or scope.

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, no annotation gaps, and an unconstrained nested query object, the description leaves the agent unable to call the tool meaningfully without first invoking describe_operation. The delegation is a partial mitigation but does not make the definition self-sufficient.

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 two parameters, including an open-ended nested 'query' object with free-form additionalProperties. The description neither names nor constrains any query parameter, deferring entirely to describe_operation, so an agent has no way to know what filters are legal without a second call.

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 essentially the endpoint path restated twice plus an operation ID, which is a tautological restatement of the name/title. It does imply a list/collection read of automation workflows, but gives no indication of what the collection contains or how it differs from siblings such as get_automation_workflows_by_id, get_automation_workflows_instances, or get_automation_workflows_condition_fiel.

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 when-to-use guidance, no exclusions, and no comparison to the many sibling automation tools. The only actionable hint is that describe_operation 'provides native request schemas', which points at a discovery step but does not say when this tool should be chosen over the by-id or instances variants.

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