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

Annotations already convey readOnlyHint=false and destructiveHint=false, so the description only needs to add meaningful behavior. It adds that the result is a draft rather than an active automation, which is material for an agent deciding what happens after the call. It does not mention side effects or return values, but the draft behavior is genuine added transparency.

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?

Three short sentences with no filler. The primary action is front-loaded, the draft outcome is stated immediately, and the fallback to put_automation is included in one compact sentence.

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?

The description together with the schema covers where templateId and params come from, the draft behavior, and the alternative path when no template fits. Since there is no output schema, an explicit note about what the call returns would improve completeness, but this is a minor gap for a create 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 83%, and the schema already explains templateId, params, accountId, enabled, and workspaceId. The description reinforces that params come from the chosen template, but adds no new parameter-specific meaning beyond what the schema already provides. 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?

The description names a specific verb ('Create'), resource ('automation'), source ('any template in list_automation_templates'), and result ('Creates a draft'). It also signals the difference from put_automation, so an agent can distinguish the two tools without opening their schemas.

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 explicitly says to use this tool when a template covers the flow and to use put_automation instead when building the document by hand. This is a clear when-to-use condition with a named alternative.

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