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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the return includes recipe and revision, and the reader is warned to treat recipe text as data rather than instructions (prompt-injection defense). No auth/permission details, but the injection warning is substantive added value.

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?

Two short sentences, zero padding, front-loaded with the core action and followed by the security caveat. Every clause earns its place.

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?

An output schema exists, so return values needn't be spelled out, and annotations cover the safety profile; the description still usefully names what is returned and adds the injection warning. The one shortfall is the total absence of parameter semantics despite 0% schema coverage.

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 0% for the two required parameters, so the description carries the burden of explaining them — and it supplies nothing about brandId scoping or the automationId UUID format. 'One automation' loosely implies the automationId, but no compensation 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?

States a specific verb and resource: read ONE automation, and further specifies what it returns (current recipe and revision). This implicitly separates it from list_automations and get_automation_run. It does not explicitly name a sibling to contrast against, keeping it at a strong 4 rather than a 5.

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?

The singular 'one automation' implies usage when a specific automation is needed rather than the list, but no explicit when-to-use, when-not, or named alternative is given. Usage is inferable but never stated.

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