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

Annotations are all false and provide no safety profile, so the description carries the full burden of behavioral disclosure. It states that an automation run is invoked but does not explain side effects, whether the run is asynchronous, what gets sent or created, or what the response contains. The example demonstrates payload shape but not behavioral consequences.

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?

The description is compact: a one-sentence purpose, a clarifying constraint on template_id, and one illustrative example. Every sentence earns its place and the key action is front-loaded.

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 and no mention of return values, failure modes, idempotency, or whether the invocation is asynchronous. For a non-read-only, non-idempotent operation, the description omits important context an agent needs to safely interpret the result of the call.

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 adds value beyond the schema by explaining that template_id must point to an existing template and by giving a concrete example that shows how data, recipient, and template_id fit together. This is genuinely useful for a tool with nested object parameters.

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 opens with a specific verb and resource: 'Invoke an automation run from an existing automation template.' It clarifies that template_id must refer to an existing workspace template, which also helps distinguish it from invoke_ad_hoc_automation. The example reinforces the purpose without ambiguity.

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 description establishes clear context: use this when you have an existing automation template and want to run it. It does not explicitly name alternatives or exclusions, such as 'use invoke_ad_hoc_automation for ad-hoc runs', but the 'existing template' qualifier makes the intended use case reasonably clear.

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