delete_mission

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

The description warns that deletion is permanent and includes all waypoints, providing essential behavioral traits. With no annotations, it fully conveys the destructive nature of the operation.

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 concise sentences: first states the action and scope, second adds a necessary prerequisite. No wasted words, front-loaded with the key 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?

For a simple one-parameter tool with no output schema, the description covers purpose, behavior, and prerequisite sourcing. It is fully sufficient for correct invocation.

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 already describes mission_id as 'The UUID of the mission to delete' with 100% coverage. The description adds the hint to use list_missions, which is helpful but doesn't add significant semantic value 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?

The description explicitly states 'Permanently delete a mission and all its waypoints,' clearly indicating the action and scope. This distinguishes it from sibling tools like list_missions or create_mission.

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?

It advises using list_missions to find mission IDs, guiding the user on prerequisites. However, it doesn't explicitly mention when not to use it or alternative deletion methods, but for a straightforward delete tool, this is adequate.

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