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 some output-shape context (that it returns current member agents, queue routing, triggers/schedules, and a `links` map), which goes beyond the annotations but does not address freshness, auth requirements, or scope.

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?

Three sentences that are front-loaded with the core purpose and finish with a minor detail about `links`. Generally efficient, though the enumerations are slightly dense and the back-reference to 'revision detail' assumes sibling familiarity.

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 single-parameter read-only tool with rich annotations and no output schema, the description gives adequate coverage of what the returned current state contains. It stops short of describing pagination or the full `links`/tab structure, but the essential invocation context is present.

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% for the single automation_id parameter, so the schema already carries the semantics. The description adds nothing about the identifier beyond what the format/pattern in the schema provides, warranting the baseline 3.

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 clear verb+resource and enumerates exactly what 'current' means: member agents with live builds, queue routing, and firing triggers/schedules. It differentiates against the revision detail via 'the revision-less counterpart,' though it does not distinguish from the related getAutomation or getAutomationCurrentFlow siblings.

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?

'An automation without revisions is read here' implies a selection condition versus the revision detail, which is useful context. However, it never names an explicit alternative tool to call instead nor states when-not-to-use, leaving the agent to infer routing to getAutomation/getAutomationCurrentFlow.

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