shelly_webhook_delete

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

The annotations only provide destructiveHint:true. The description adds two behavioral traits beyond annotations: the requirement for confirm:true (a safety guard) and that the operation is audit-logged. This provides useful context for an AI agent deciding to invoke the tool.

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: one sentence with three clear clauses. It is front-loaded with the primary action, followed by two critical usage notes. No unnecessary words.

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 complexity (simple delete with 3 params) and the existence of an output schema, the description covers the core action and key behavioral aspects (confirm, audit). However, it lacks details about the 'device' parameter and the response structure, which the output schema may address, but the description does not fully ensure the agent can call the tool correctly without guessing.

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 explains the 'id' parameter (delete by id) and the 'confirm' requirement, but does not clarify the 'device' parameter. With three undocumented parameters, this is insufficient.

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 a webhook' by id. The verb 'delete' and resource 'webhook' are specific, and the sibling tools (e.g., shelly_webhook_list, shelly_webhook_create) are distinct, making the purpose unambiguous.

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 includes the requirement 'confirm:true', indicating that deletion only occurs with explicit confirmation, which helps the agent avoid accidental destructive actions. It does not explicitly contrast with sibling tools, but the name and context imply 'use this to delete a webhook, not to list or create'.

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