openwisp_delete_device_location

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

No annotations are provided, so the description carries the behavioral burden. 'Remove the location from a device' plus the DELETE verb signals a destructive, non-reversible mutation, but it doesn't state whether removing the association deletes the location entity, what happens if no location is set, or whether it requires permissions. A note on irreversibility would meaningfully help.

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?

One short sentence plus the endpoint in parentheses, with no filler. The category tag adds minor clutter but the statement is front-loaded and efficient.

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 of a device-location association with one fully documented parameter, the description covers the essential mechanics. Missing context includes whether the location entity is preserved, error behavior when no location is assigned, and required permissions — but the core is adequate.

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 coverage is 100% and the single 'id' parameter is documented ('Device UUID or ID'). The HTTP path template {id} reinforces that this is the device identifier, not the location id — a subtle but useful disambiguation. No additional meaning is needed beyond the schema.

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 specific verb (delete/remove) and resource (device location), clearly distinguishing it from siblings like openwisp_get_device_location, openwisp_create_device_location, and openwisp_update_device_location. The bracketed category tag is noise but the core purpose is 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?

No guidance on when to use this versus alternatives such as openwisp_delete_location (which deletes the location entity itself) or openwisp_update_device_location. An agent must infer that this removes only the association, not the location record.

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