qui_preview_automation_delete

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

With no annotations, the description must disclose behavior, but it does not state whether this operation is a dry-run preview, a destructive delete, or what side effects occur. The contradictory signals from the name ('delete') and endpoint ('preview') are left unresolved.

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 two short sentences, front-loaded with the endpoint, and contains no filler or redundant information.

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?

Despite having an output schema, the tool has a single free-form parameter and no annotations, so the description must provide meaningful context. It only covers the API call envelope and leaves out the endpoint's purpose, safety profile, and interaction with the 'delete' operation, making it incomplete for an agent to use safely.

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?

The description adds useful structure to the otherwise free-form 'arguments' parameter by specifying that path variables go directly in arguments, query values in arguments.params, and body in arguments.body. However, it does not enumerate the specific fields for this endpoint, so it only partially compensates for the 0% schema coverage.

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 only says to call a specific endpoint without explaining what the tool does functionally. It does not clarify what 'delete' means in the tool name or what an automation preview entails, making it hard to distinguish from siblings like qui_delete_automation or qui_apply_automations.

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?

No when-to-use guidance or alternatives are mentioned. The description focuses on how to pass parameters, not when to choose this tool over others like qui_delete_automation or qui_dry_run_automations.

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