shelly_schedule_delete

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

The description adds 'Audit-logged' beyond the destructiveHint annotation, providing extra behavioral context. It does not contradict annotations.

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, no fluff. Essential information is front-loaded: what it does, the requirement, and an extra behavioral note.

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 deletion tool with output schema and destructiveHint annotation, the description covers purpose, a key requirement, and audit-logging. It is sufficient but could mention error handling or confirmation necessity.

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 explains the `id` parameter as the schedule identifier and explicitly mandates `confirm:true`. However, the `device` parameter is not described, and with 0% schema coverage, more detail would be beneficial.

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'), the resource ('a schedule'), and the identifier ('by `id`'). This distinguishes it from sibling tools like shelly_schedule_create, shelly_schedule_update, etc.

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?

It explicitly requires `confirm:true`, which is a crucial usage precondition. While it doesn't mention alternatives, the requirement is clearly stated, aiding correct invocation.

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