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

The annotations already declare destructiveHint=true and idempotentHint=false, and the description builds on that with concrete consequences: the mission is marked FAILED, no reward is paid, ship_status is reset to IDLE, a mission slot is freed, and all progress is lost irreversibly. This goes well beyond the generic hints.

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?

Three tightly packed sentences lead with the effect, then the state reset, the irreversibility warning, and finally a usage example. Nothing is redundant and the most decision-relevant facts (no reward, irreversible) come early.

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 destructive one-parameter mutation with no output schema, the description covers the outcome and the irreversibility. The remaining gap is failure behavior (unknown or already-terminal mission_id, wrong ownership), but otherwise an agent has everything it needs.

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 100% and covers both the bearer fallback and 'player_mission_id to abandon', so the schema explains most of the meaning. The description only adds the qualifier that the mission must be 'active', qualifying a parameter whose semantics are already documented, so the baseline of 3 applies. For example, it does not say what happens if the ID is already FAILED or COMPLETED.

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 names a specific verb and resource ('Abandon a ... active mission') and immediately states its effect: marks it FAILED, grants no reward, and resets ship_status to IDLE. This clearly distinguishes it from siblings like complete_mission, accept_mission, and cancel_order (which is for orders, not missions).

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 states when to use it ('stuck or unwanted active mission') and gives a concrete scenario: escaping a COMBAT mission accepted in a High-Sec sector where no pirates are reachable. There is no explicit 'when not to use' or named alternative, but the domain is clear enough that an agent can select it confidently.

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