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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower; the description adds the required API-key scope (`automations:read`) and describes the payload shape (triggers, condition tree, actions). It omits behavior for an unknown identifier (error/404) but adds real value beyond annotations.

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 short sentences: purpose first, return payload second, auth scope last. Nothing is redundant and nothing is buried.

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 names the returned DTO and its key sections, and it discloses the required scope. Minor gap: no mention of what happens when the automation is missing or inaccessible via the workspace/account override.

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%, including detailed docs for the account and workspace override parameters, so the schema carries parameter semantics. The description only restates that the identifier is an automation identifier, adding no format or format-edge guidance beyond the schema's `auto_…` hint.

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 and resource ('Fetch a single automation by identifier') and clarifies cardinality, which implicitly separates it from the pm_list_automations_for_space/list/folder siblings. It does not name an alternative tool, but the singular-by-ID framing is unambiguous.

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: retrieve one automation when you already have its identifier, versus the list tools when you don't. No explicit when/when-not statement or named alternative is given, so the agent must infer the routing.

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