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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description earns credit by disclosing the shape of the returned data (counts, tab arrangement, current links) even though there is no output schema to convey it, though it says nothing about not-found behavior or auth requirements.

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 that packs in the return payload without filler. Slightly dense and backtick-heavy, but every clause carries information.

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 usefully compensates by describing what comes back, and annotations cover the operation's safety profile. It is essentially complete for a simple read-by-ID tool, with only error/not-found semantics left unspecified.

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?

There is one parameter and schema description coverage is 100%, so the schema fully documents automation_id. The description adds no format or constraint detail beyond what the schema provides, so the baseline of 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 ('Get') and resource ('a single automation') and goes on to enumerate the payload components: agent/queue counts, tab arrangement, and per-tab links. It is clearly distinct from listAutomations, but it does not explicitly differentiate itself from close siblings like getAutomationCurrent or getAutomationTabs.

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 implied rather than stated: an agent can infer this fetches one automation by ID, and the 'single' wording implies the list alternative. However, it gives no when-to-use guidance relative to getAutomationCurrent, getAutomationTabs, or getAutomationCurrentFlow, nor any preconditions.

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