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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context on top: the meaning of `running` (live work, answers reach Agents from their next run), the `structural` binding implication, the ban on inventing answers for open questions, and the instruction to surface full URLs. None of this is derivable from the structured fields.

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?

Front-loads the purpose well, but the body is one dense run-on with heavily chained clauses (counts, module_defaults, pending_apply, running, bindings) that is hard to scan. Every element is arguably relevant, yet it would benefit from being broken into shorter, structured sentences.

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?

There is no output schema, so the description carries the full burden of describing return values — and it does so field by field, including nested concepts like counts.questions, module_defaults, pending_apply and urls. An agent has everything needed to call it and interpret the result.

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 automation_id and include_hidden are already documented, and the enum on include_hidden is self-explanatory. The description explains the returned `id` field's link to updateConfigField but says nothing about the two input parameters beyond what the schema provides.

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 an automation's whole Policy') and then enumerates the return payload by name — questions by section, counts.questions, module_defaults, pending_apply, urls — which lets an agent distinguish it from getAutomation, getAutomationCurrent and readAutomationDashboardData without opening a schema.

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?

Gives a clear trigger ('before answering anything about it') and conditional rules for the running case ('change it only after the user says yes') plus the structural-bindings follow-up. It does not name an alternative sibling to use instead, so it stops short of full when/when-not routing.

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