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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent, open-world mutation, so the description's contribution is the whole-replacement semantics for trigger/steps plus the supported template vocabulary - both are real behavioral facts not present in structured fields. It still omits whether unmentioned fields are preserved and what the call returns.

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 sentences, front-loaded with the four actions an agent can perform, followed by one dense but high-value reference list. No filler, no restatement of the tool name or title.

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?

For a nested, open-world mutation with no output schema, the definition still leaves gaps: baseId is undocumented, the return value is never described, and the conditions under which the template list applies (values/body/prompt/filter) are left implicit. Adequate to call it, but not complete.

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?

With schema coverage at only 17%, the description compensates well at the top level: name = rename, enabled = on/off, trigger and steps = whole replacement, and the template list supplies the substitution syntax ({{steps.<id>...}}, {{trigger.record.<Field>}}) that the schema never states. The required baseId parameter remains entirely unexplained in both description and schema, and the template list is undifferentiated rather than mapped to specific fields.

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 description uses specific verbs and enumerates exactly what can be mutated: rename (name), switch on/off (enabled), replace trigger, replace steps. That maps cleanly onto the mutation parameters and distinguishes it from read-oriented siblings like get_automation/list_automations without naming them explicitly.

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 parenthetical '(each is replaced as a whole when given)' is a useful usage cue for trigger and steps, implying omitted fields are left alone and that a single-step edit requires resubmitting the whole array. However, there is no explicit when-to-use guidance, no mention of reading current state with get_automation first, and no comparison to create_automation.

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