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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: missions are generated on demand and refresh periodically, station ownership filters the board, the fixer account is shared across stations, and it enumerates the returned fields (type, objectives, rewards, time limit). The cargo_liability and restitution_relief notes describe acceptance-time mechanics rather than this read call, which is slightly off-target but not contradictory.

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 purpose is correctly front-loaded in the first clause, but the rest is a single oversized parenthetical that mixes tool-selection facts (docking requirement, station scoping) with peripheral economy mechanics (fixer account sharing, cargo_liability reservation, restitution_relief capping). Several of those sentences do not help an agent decide to call or how to call this tool.

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 one-parameter read tool with no output schema, the description covers the prerequisite, the dynamic nature of the results, and the shape of the return values, which is what an agent needs. The remaining gap is authoritatively separating it from the other mission-listing tools.

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% for the single session_id parameter, so the schema carries the full burden and the description adds nothing parameter-specific. This is the baseline 3 for a fully documented single-parameter tool.

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?

"Get available missions at your current base" gives a specific verb and resource, and the word "available" meaningfully separates it from the accepted/completed mission tools in the sibling list (get_active_missions, completed_missions, view_completed_mission). However, it never names those siblings, so the agent must infer the boundary rather than being told it.

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 states a hard precondition ("You must be docked at a base with mission services") and a scoping rule for player-owned stations, which is useful invocation context. But it offers no routing guidance against alternatives such as get_active_missions, faction_list_missions, or accept_mission, so when-to-use is only implied.

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