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

With only readOnlyHint=false in annotations, the description carries the burden of behavioral disclosure. It adds the location prerequisite, the active-mission cap, and the special distress-mission case. It does not mention failure behavior or response details, but the most important behavioral constraints are disclosed.

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 description is front-loaded with the core action and then packs necessary constraints into a compact parenthetical. It contains no filler or repeated schema information, though the parenthetical could be slightly better structured. Still, every sentence earns its place.

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 mutating action with three parameters and no output schema, the description covers the prerequisite, the exception, the active-mission cap, and where to find IDs. An agent has enough context to decide when to call this tool and how to supply the required mission identifier.

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 the baseline is 3. The description adds value by explaining that distress missions are claimed specifically by mission_id from anywhere, and by pointing to get_missions as the source for available mission IDs. This goes slightly beyond the schema's parameter descriptions.

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 states a specific action and resource: 'Accept a mission from the mission board.' It adds meaningful scope by describing the docked requirement and the emergency-broadcast exception, which clearly differentiates this from mission-related siblings like decline_mission, abandon_mission, or complete_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?

The description explicitly explains when the tool can be used: only while docked at the issuing base, with a clearly stated exception for distress-response missions. It also gives an operational cap ('Maximum 5 active missions at once') and directs the agent to get_missions for mission IDs, giving enough context for correct selection and invocation.

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