delete_device

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

The annotations already mark the operation as destructive and not read-only. The description adds meaningful behavioral context by requiring write permission and clarifying that deletion is soft by default, which is important for an agent deciding whether to proceed.

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, front-loaded sentence with no wasted words. It conveys the core action, a permission prerequisite, and the default deletion behavior efficiently.

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 delete operation with well-covered parameters and destructive annotations, this is largely complete. It could be improved by mentioning recovery options or consequences for associated resources, but nothing essential is missing for choosing and invoking the tool.

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 input schema already fully documents both parameters, including the default for delete_hard. The description adds the 'soft delete' framing, reinforcing the delete_hard behavior, but does not materially expand on what the schema already states.

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 the specific action 'Delete a device/resource' and the key default behavior 'Soft delete by default.' It is clear about the resource and operation, though it does not explicitly differentiate from siblings like delete_device_instance or bulk_delete_devices.

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 implies usage when a device needs to be deleted, and the soft-delete default provides some context. However, it gives no guidance on when to choose this tool over alternatives such as bulk_delete_devices or recover_device.

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