delete_device

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the destructive blast radius ('Cascades to all entities of that device') and the important non-permanence trait that discovery may re-add the device. It stops short of permissions, confirmation, or reversibility details.

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?

Three short sentences, front-loaded with the core action and immediately followed by the two consequences that matter. No filler or restatement of the tool name.

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 no-annotation, no-output-schema delete tool, the cascade and re-add behavior are exactly the behavioral facts an agent needs. Missing only auth/permission requirements and explicit confirmation guidance, which keeps it short of full completeness.

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% for the single device_id parameter, so the description technically should compensate, but it adds nothing about identifier format or source. Given only one self-evident parameter, this is a minor gap rather than a harmful one.

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?

States a precise verb+resource+scope: 'Remove a device from the registry'. This separates it cleanly from siblings like delete_registry_entity, update_device, and list_devices without requiring the agent to open any schema.

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?

Usage is implied (remove a registered device), and the note that 'the owning integration may re-add it on next discovery' is a useful caveat for deciding whether deletion is worthwhile. However, it never states when to prefer this over alternatives such as disabling the config entry or deleting the registry entity.

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