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

With no annotations, the description carries the full burden and does so richly: it enumerates trigger types, exact schedule intervals, the Prague time zone, step execution order and `next` null semantics, the three step types, what `message` means, that ids are user-authored, and what the call returns (id, editor link, what's missing). This is far beyond the schema's structural hints.

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?

It is front-loaded with the create/replace action, then usage, then mechanics, and nearly every clause carries distinct information. The prose is dense and run-on with stacked parentheticals, which costs it clarity, but the length is defensible for a nested schema of this complexity.

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?

No output schema exists, and the description compensates by saying it returns the id, editor link, and what is missing. It covers trigger, steps, and enablement well; the `agent` parameter's role is left to the schema, a minor gap for such a broad 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 100%, so the baseline is 3; the description still adds meaning beyond it, notably the Prague-time schedule convention, the allowed cadence list, and the plain-words semantics of a 'send' step's message (brief vs finished text vs empty). Some fields like `agent` are only explained in the schema, holding it at 4.

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 opening sentence states a precise verb and resource ('Create an automation... or replace one (give its id)'), clearly separating the create and update paths. It does not explicitly name sibling tools like automation_enable or automation_run, but the create/replace framing makes the scope 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?

It gives concrete triggering conditions for when to use it ('the owner asks for it', 'anything recurring... or after they said yes to its offer'), which is strong context. It stops short of naming an alternative tool to use instead, so it lacks the explicit when-not/alternative routing of a 5.

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