shelly_virtual_delete

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

Annotations already provide destructiveHint:true, so the destructive nature is clear. The description adds value by requiring 'confirm:true' for the operation, which is a behavioral trait beyond the annotation. No contradiction detected.

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 a single concise sentence that front-loads the main purpose. Every part earns its place with no superfluous 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?

The description covers the essential aspects: action, resource, key format, and the confirm requirement. Given that an output schema exists and annotations mark it destructive, the description is largely complete for a delete operation, though the missing device parameter info is a minor gap.

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?

With 0% schema description coverage, the description must compensate. It explains the key parameter format ('<type>:<cid>') and implies the confirm parameter must be true, but the device parameter is not described at all. This provides partial but incomplete parameter guidance.

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 'Delete a virtual component by key' with the key format specified as '<type>:<cid>'. It directly conveys the action and resource, distinguishing it from sibling tools like shelly_virtual_list (list) and shelly_virtual_add (add).

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 explicitly mentions 'Requires confirm:true', giving a clear prerequisite for deletion. However, it does not provide guidance on when to use this tool versus other delete tools (e.g., shelly_kvs_delete, shelly_scene_delete) or when not to use it.

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