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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral detail beyond that — the response includes a step-by-step timeline — but says nothing about what happens for an unknown or expired run_id.

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?

A single front-loaded sentence with zero filler; the resource and the notable return characteristic (timeline) are both stated immediately.

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 two-parameter read tool with complete annotations, the description is adequate but thin. With no output schema, it could do more to characterize the returned run (status, timestamps, step data) and to point at list_automation_runs for discovering run_ids.

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%, so both parameters are documented as 'Automation id' and 'Run id'; baseline 3 applies. The description does not disambiguate the relationship between the two IDs (e.g. whether run_id alone would suffice) or note that both are required.

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 ('Retrieve one run') and adds scope detail ('with its step-by-step timeline'). It is implicitly distinct from list_automation_runs (many runs) and get_automation (the automation itself), though neither sibling is named.

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 only implied: the agent must already hold a run_id, which suggests reading a known run rather than discovering runs. There is no explicit instruction to call list_automation_runs first to obtain the run_id, and no stated exclusions.

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