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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered. The description adds substantial domain context beyond that: the meaning of each terminal and blocked status, that blocked_ai_quota resets at 00:00 UTC, and that AI failure reasons appear in the log as classify_failed or ai_failed. It does not disclose pagination behavior for the limit/before parameters.

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?

Front-loaded with a single clear sentence stating what is returned, followed by the status enumeration. The long parenthetical list is dense but earns its place because no output schema exists to document these values elsewhere; minor sprawl keeps it from a 5.

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, the description usefully covers return semantics (statuses and step log), and annotations cover the safety profile. However, the undocumented limit/before pagination parameters and the required id parameter leave an agent without guidance on result size or how to page through runs.

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 only 25% (only workspaceId is documented). The description explains status values, which are output semantics rather than parameters, and says nothing about id, limit, or before (pagination). With four parameters and a large coverage gap, the description fails to compensate.

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?

States a specific verb and resource with scope ('Runs of one automation') and names the two things returned ('status and a step log'). It is clearly distinguishable from list_automations, get_automation, and list_automation_versions without opening any schema.

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?

Usage is implied: you need one automation's id to retrieve its run history, and the status list hints at debugging why a run stopped. But there is no explicit when-to-use statement, no comparison to get_automation or list_automation_versions, and no prerequisites (e.g., required permissions).

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