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

With no annotations and no output schema, the description carries the full burden and does disclose the return contents (save-form automation, what's missing, last runs with each step's answer), which is genuinely useful. However it says nothing about permissions, whether the read is safe/non-mutating, or pagination/limits on the runs list.

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 sentence with no wasted words, front-loaded on the core action. The nested clauses (save-form, missing, runs) make it slightly run-on but every element 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?

Given no output schema and no annotations, the description does the important work of describing what is returned, including the automation_save-compatible form and the run/step detail. It is nearly sufficient for calling correctly, missing only safety and limit context.

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%, so the schema already documents both parameters, including that id comes from automation_list. The description adds no parameter-level meaning beyond the schema, so the baseline 3 is appropriate.

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+resource ("Show one automation") and goes further by naming the exact representation returned (the automation_save form) and the supplementary payloads (missing fields, last runs). This distinguishes it from the plural automation_list and from automation_save, though the phrasing is somewhat dense.

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 only implied: "edit it and save it back with the same id" sketches a read-then-save workflow with automation_save, but there is no explicit statement of when to choose this over automation_list or automation_run. The agent must infer the round-trip use case.

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