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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description earns credit for disclosing the payload shape beyond annotations: trigger and steps resolved to table/field names, optional webhook URL, and a bounded last-20-runs history, which tells the agent this is a detail fetch with embedded run data rather than a raw config dump.

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 returned content front-loaded and no filler. It is a grammatical fragment rather than a complete sentence, but nothing 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?

With no output schema, the description must carry the return-value burden and does so partially (trigger, steps, webhook, 20 runs). It leaves out how the two required parameters are used and how this differs from list_automations, which are the main remaining gaps for a 2-param read tool.

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 50%: the 'automation' param documents 'name or id' but baseId is undocumented. The description says nothing about either parameter — not that automation accepts a name or id, not that baseId scopes the lookup — so it fails to compensate 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?

The description enumerates what comes back (trigger, steps, webhook URL, last 20 runs) which pins the resource to a single automation, but it is a noun phrase with no verb and never distinguishes itself from the closely named sibling list_automations or from update_automation. An agent can roughly infer retrieval, but the intent is implied rather than stated.

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?

There is no guidance on when to call this versus list_automations (to discover automations) or update_automation. No prerequisites, no preconditions, no exclusions are mentioned.

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