automations_delete_script

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

With no annotations provided, the description carries full burden. It discloses one behavioral trait: auto-reloads scripts after deletion. But it omits crucial details like whether the deletion is permanent, what happens to automations referencing the script, required permissions, or confirmation behavior beyond setting confirm=True. Incomplete for a destructive operation.

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 extremely concise with two sentences, front-loading the action and key behavioral notes. Every word is functional, with no redundancy or filler.

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?

Given the tool's simplicity (delete script with confirm) and the presence of an output schema (not shown), the description covers the core purpose and a key behavioral note. However, it lacks details on side effects, reversibility, or return value, leaving gaps for an agent to fully understand the operation's context.

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 description coverage is 0%, so the description must compensate. It mentions 'by id' for script_id and 'Set confirm=True' for confirm, but does not explain the format, constraints, or examples for script_id. The semantic value added is minimal, leaving ambiguity about valid values.

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 action 'Delete' and the resource 'script by id'. It also adds 'Auto-reloads scripts afterwards' to differentiate from similar delete tools. The purpose is unambiguous and distinct from siblings like automations_delete_automation.

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 provides the guideline 'Set confirm=True to proceed', which is a specific usage condition. However, it does not explain when to use this tool over alternatives like automations_disable_automation or how to ensure the correct script_id. Lacks explicit when-not or context for typical scenarios.

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