device_delete

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

Annotations already flag destructiveHint=true, and the description adds the concrete scope that all stored ChirpStack data associated with the device is deleted. This goes beyond the generic destructive flag by clarifying the blast radius, though it doesn't mention reversibility or auth requirements.

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, efficiently worded sentence with no filler. It front-loads the action and scope.

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 one-parameter destructive tool with a clear annotation and an output schema, the description conveys the essential behavior. It could mention irreversibility or prerequisites, but the combination of annotations and description is sufficient for an agent to understand what will happen.

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%, and the description does not explain the dev_eui parameter or how to identify the target device. The parameter name is self-explanatory, but the description itself adds no meaning beyond the bare schema field.

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 states the specific verb 'Delete' and resource 'device', and adds the clarifying scope 'everything ChirpStack stores about it,' which distinguishes it from sibling tools like device_deactivate that imply a less destructive operation. This gives an agent a precise understanding of what the tool does.

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 explicit alternatives or when-to-use guidance is provided; the description only implies that this is for complete device removal. The agent must rely on sibling names and context to distinguish it from device_deactivate or device_flush_dev_nonces. This leaves usage decisions to inference.

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