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. The description adds no behavioral context such as pagination, filtering, or what an 'instance' represents; the 'describe_operation provides native request schemas' note is the only added information and concerns discovery, not behavior.

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?

Short but wasteful: the identical path is printed twice, and the operation ID is noise for an agent. There is no front-loaded statement of purpose or return content.

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?

A nested-object tool with 0% schema coverage, no output schema, and no annotations gap-filling leaves the agent without any information about request shape or response content. The description does not fill that void at all.

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 0% and the two parameters (a free-form 'query' object with additionalProperties and an empty 'params' object) are entirely undocumented. The description does not compensate; it only refers the agent to describe_operation, leaving the actual semantics unexplained.

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 only the raw endpoint path 'GET /api/automation-workflows/instances' repeated verbatim, which restates the tool name and title rather than explaining what it returns. An agent can infer it lists automation workflow instances, but nothing distinguishes it from get_automation_workflows or get_automation_workflows_instances_by_id beyond the URL shape.

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?

No guidance on when to use this versus the sibling list/detail tools, no prerequisites, no exclusions. The only directive is a pointer to describe_operation for schemas, which is about parameters, not tool selection.

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