delete_drone

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

Discloses that the action is irreversible ('cannot be undone') and describes failure conditions ('Fails if the drone is currently referenced by any missions'). No annotations provided, so the description carries full burden and meets it.

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?

Two sentences conveying irreversibility, failure condition, and prerequisite. No redundant information.

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?

Given only one parameter, no output schema, and detailed behavioral notes, the description is complete for this destructive 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?

Schema has 100% coverage with a clear description for drone_id. The description adds context about usage constraints but does not elaborate on the parameter format beyond the schema, so a 4 is warranted.

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 'Permanently delete a drone profile' using a specific verb (delete) and resource (drone profile), distinguishing it from siblings like update_drone or create_drone.

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?

Explicitly mentions when the tool cannot be used ('Fails if the drone is currently referenced by any missions') and provides guidance on prerequisites ('unlink it from missions first').

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