Delete a HomeyScript script

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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds valuable context beyond annotations: 'no undo,' 'any Flow that started it stops working,' and that the code is returned in the result for recreation. These are meaningful behavioral disclosures that help the agent understand side effects and recovery.

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 three sentences: the first states the action, the second highlights irreversibility and side effects, the third explains a recovery mechanism. Every sentence carries essential information without fluff or redundancy.

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?

For a simple delete tool with one parameter and no output schema, the description covers all critical aspects: what it does, irreversibility, impact on flows, and the returned code for recovery. This is sufficient for an agent to decide and invoke the tool correctly.

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 schema covers the single parameter with a description ('The script id, or its exact name'), achieving 100% coverage. The tool description does not add any extra parameter-specific meaning. Since the schema already documents the parameter, the baseline of 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 clearly states the action: 'Removes a script from the Homey.' It uses a specific verb ('removes') and resource ('script'), and it distinguishes itself from siblings like homey_script_get or homey_script_update by focusing on deletion. Additional consequences (no undo, flows stop) reinforce its unique purpose.

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 usage context is implied: use this tool to delete a script. However, there is no explicit guidance on when to prefer this over alternatives, or prerequisites like fetching the script first. It does mention the recovery option (code returned), but lacks clear when-to-use vs. when-not-to-use statements.

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