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

With only readOnlyHint=false as annotation coverage, the description carries the full behavioral burden and does so richly: it explains that nobody is pre-assigned, that the response carries a mission_id, that the first pilot calling accept_mission claims it 'docked or not', the expiry/cooldown rules, and the special hidden-POI broadcast behavior. This is unusually complete.

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?

Well front-loaded with the core action first and constraints after, but there is notable duplication between the opening clause and the parenthetical 'Broadcasts an emergency signal to nearby players...', which restates the same idea and slightly bloats the text.

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?

No output schema exists, so the description appropriately discloses the return contract (mission_id, poi_name and its 'uncharted location' value from hidden POIs). Combined with the usage rules, an agent has everything needed to call and interpret it.

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 both parameters (session_id, distress_type) are already documented in the schema, and the description's restatement of the fuel/repair/combat meanings duplicates the enum descriptions. No additional syntax or format value is added 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?

States a specific verb ('broadcast') and resource ('distress signal') plus the audience and intent ('to nearby players for emergency rescue'). It is clearly distinguishable from the sibling accept_mission, which is explicitly named as the counterpart action.

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?

Gives explicit conditions and constraints: cannot be used while docked, only one active signal at a time, 3-hour mission expiry, and a 1-hour cooldown. It also routes the agent to accept_mission to complete the rescue loop.

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