delete_drone

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

With no annotations provided, the description fully discloses that deletion is permanent, irreversible, and fails under certain conditions (referenced by missions). This provides complete behavioral transparency beyond what annotations would convey.

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 with no wasted words. The first sentence states the core action, and the second adds critical detail. Properly front-loaded.

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?

The description covers purpose, irreversibility, and a key failure condition. Without an output schema, it could mention the response on success, but for a delete tool, this is adequate and nearly complete.

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 schema provides 100% coverage for the single parameter drone_id. The description adds context about deletion behavior but does not add further meaning to the parameter beyond what the schema already states. Baseline is 3.

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' with a specific verb and resource. It distinguishes from siblings like create_drone, update_drone, and delete_mission by explicitly naming the action on drone profiles.

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 provides a crucial usage condition: 'Fails if the drone is currently referenced by any missions — unlink it from missions first.' This informs the agent of a necessary prerequisite but does not explicitly discuss when to use or compare to alternatives.

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