Stopping a automation

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

Annotations already mark destructive=true; description adds context about aborting remote actions and required permission. Could elaborate on post-stop state but adequate.

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 purpose. First sentence is slightly redundant with title, but overall efficient and clear.

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?

With output schema present and annotations, description covers purpose, permission, and effect. Missing potential error cases or prerequisites, but sufficient for a destructive action 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 100%, so baseline 3 applies. Description does not add detail beyond schema for parameters like instance_id or confirm, but permission hint is additional context.

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 clearly states the tool stops an automation instance and aborts actions on a remote endpoint, distinguishing it from siblings like delete_automation or create_automation_instance.

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 implies using this tool to stop a running automation, but lacks explicit guidance on when to use vs alternatives like pause or delete. Permission requirement is mentioned.

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