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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the behavior that it returns status and trigger info, but does not disclose potential pagination, default sorting, or whether archived workflows are included. This is adequate but not rich context beyond 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 a single, concise sentence that front-loads the purpose and includes relevant output details. It contains no filler or redundant information, earning a perfect score for conciseness and structure.

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 simple read-only list operation with well-documented optional parameters and no output schema, the description is fairly complete. It states the primary purpose and the returned information. It lacks explicit mention of pagination or ordering, but these are not critical for the core use case. The combination of description, schema, and annotations provides sufficient context.

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% for both parameters (active and triggerType), so the schema already explains their meaning. The description does not add any additional parameter context. With high schema coverage, the baseline is 3, and the description neither enhances nor detracts from parameter understanding.

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 'List all automation workflows with their status and trigger info' uses a specific verb (list) + resource (automation workflows) and clearly states scope ('all') and the included information (status, trigger info). It distinguishes from sibling tools like list_workflow_runs, which lists runs rather than workflows, and get_workflow_run, which retrieves a specific run.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention, for example, that list_workflow_runs is for workflow executions, or that get_workflow_run provides details on a single run. Users/agents are left to infer the appropriate context from the tool name and siblings.

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