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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no mention of pagination behavior, default sort order, or result size characteristics that an agent would need to plan calls.

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 tight sentence with the purpose front-loaded and no filler. It is arguably under-sized for a seven-parameter list tool, but nothing in it is wasted.

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?

No output schema exists, so the description should give some sense of what is returned (automation records with status/context, presumably), pagination shape, and default ordering. Annotations cover read-only safety, and the schema covers page/per_page bounds, but the return-value and sorting behavior remain undocumented.

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 43%, and the description names three of the seven parameters (name, status, context) as filter dimensions, which helps orient the agent. However, it says nothing about sort/order semantics, matching behavior for 'name' (substring per schema), or how pagination interacts with results, so it only partially compensates for the coverage gap.

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 ('List') and resource ('automations') and names the filter dimensions (context, status, name). It does not distinguish itself from nearby siblings like list-automation-runs or get-automation, but the gap is small given the naming is self-descriptive.

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?

Mentions that filters exist, implying use for filtered enumeration, but never says when to prefer this over get-automation or list-automation-runs. No exclusions, prerequisites, or clarifying context are given.

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