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 carries little weight here. The description contributes the meaningful extra fact that results are ordered newest first, but says nothing about pagination behavior despite exposing a cursor, nor about what a run record contains.

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 short sentence, front-loaded with the operation and ending with the sorting behavior; nothing is wasted. It is arguably too terse rather than too long, but it is efficient and well ordered.

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 paginated list tool with full schema coverage and no output schema, the essentials are present. Still missing is any routing hint versus get_automation_run and list_automations, and a note that cursor drives paging, which would make the definition self-sufficient.

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% — id, limit (default 25, max 100) and cursor (next_cursor from previous page) are all documented in the schema. The description adds no parameter-level detail beyond what is already structured, so the baseline 3 applies.

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+resource ('List an automation's runs') and adds the ordering ('newest first'), so the intent is unambiguous. It does not explicitly distinguish itself from nearby siblings such as get_automation_run or list_automations, though the scope (runs of one automation) is implied by the possessive.

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 statement of when to use this versus get_automation_run (single run) or list_automations (automations rather than runs). The agent must infer the selection rule from the resource noun alone.

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