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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description earns credit for going beyond that by disclosing the returned payload — trigger, conditions, steps in order, per-step wait, and counts of members en route/finished/stopped. It does not cover lookup failure behavior or whether name matching is case-insensitive (the schema does), which keeps it short of a 5.

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?

It is short, but it is written as a fragmentary run-on that opens with a prepositional phrase rather than the action, and the mid-sentence digression about post_id / get_post / edit_post interrupts the enumeration of returned fields. The core content is useful; the structure is awkward and not front-loaded.

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 must describe the return value, and it does so in reasonable detail: trigger, conditions, ordered steps, per-step waits, and member counts. Missing are failure/empty cases and any hint about response size for long automations, but for a 2-parameter read tool this is largely 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 coverage is 100% and both parameters are documented in-schema, including 'id, or its name in any case', so the schema already does the heavy lifting. The description adds only a mild restatement — 'named in site' and 'one automation' — without extra syntax, format, or resolution-order detail. 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?

The description identifies the resource precisely — a single automation on one site — and enumerates its constituent parts (trigger, conditions, ordered steps, waits, member counts), so an agent knows exactly what comes back. It never states the verb explicitly (the 'get' is only in the name/title), and the parenthetical about post_id being something get_post and edit_post 'read and change' is tangential rather than differentiating.

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 enumeration of returned data and the read-only nature signal 'inspect one automation,' and the site-scoping clause hints at the account/site requirement. There is no explicit guidance on when to call this versus update_automation, get_build, or other siblings, and no stated preconditions such as the automation needing to exist.

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