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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context by explaining the meaning of status values (blocked_window, blocked_opt_out, etc.), but it does not disclose pagination behavior, ordering, or other operational details like rate limits.

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 compact and front-loaded with the core purpose, followed by a valuable enumeration of statuses. Each line earns its place, though the long status list could arguably be trimmed if a separate enum were available; here it is necessary.

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?

The tool has 4 parameters, no output schema, and very low schema coverage, so the description must carry substantial weight. It covers the output's nature and status meanings but leaves pagination parameters and return details unspecified, making it incomplete for an agent to call correctly in all cases.

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 only 25%, so the description must compensate, but it only implicitly clarifies that 'id' refers to the automation. The 'limit' and 'before' pagination parameters are left entirely unexplained, and workspaceId's purpose is defined only in the schema, not the description.

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 clearly identifies the resource (runs of one automation) and the output (status and step log), and the title supplies the verb 'List'. It differentiates from siblings like list_automations and get_automation by specifying 'one automation', though the description itself is a noun phrase rather than a full verb-led statement.

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 explicit guidance is given about when to use this tool versus alternatives such as list_automations or get_automation. The status meanings imply use for inspecting run history, but there is no stated context, prerequisites, or exclusions.

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