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

With only readOnlyHint=false in annotations, the description carries the behavioral burden and does so thoroughly: it explains cargo retention, courier good reclamation, smuggling debt persistence, wallet-capped charges for other missions, expiry equivalence, and concrete debt settlement paths.

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 main action is front-loaded, and most of the dense parenthetical content earns its place by explaining non-obvious consequences. It is longer than typical but largely justified by the complexity of debt and cargo rules.

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?

There is no output schema and minimal annotations, so the description must explain consequences and follow-up behavior. It covers removal, cargo handling, debt rules, expiry, and the two ways to settle debt, making it complete enough for an agent to call correctly.

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 coverage is 100%, so mission_id and session_id are already documented in the schema. The description adds no parameter-level detail beyond what the structured schema provides.

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 opens with a specific verb and resource: 'Abandon an active mission.' It immediately clarifies scope by saying the mission is removed from the active list, which distinguishes it from mission completion/acceptance siblings even though it does not name them directly.

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?

Usage is implied by 'active mission,' and the description gives important post-abandon consequences. However, it does not explicitly compare this tool against alternatives such as decline_mission or complete_mission, so an agent must infer when abandoning is preferable.

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