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

Goes well beyond the lone readOnlyHint=false annotation, disclosing error semantics (player_not_found for unseen or unknown targets), capacity requirements for explicit injured transfers, the one-fit-crew-must-remain rule, and an atomic same-class swap behavior when the recipient is full. These are exactly the mutation-side traits an agent needs.

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?

Front-loads the core action and conditions in the first clause, then appends error and edge-case detail in compact parentheticals. Dense but each sentence carries useful information; slightly heavy for a single paragraph.

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?

With no output schema, the description adequately covers preconditions, failure modes, capacity, and the swap edge case for a mutation tool. Minor gap: no indication of success response or what the receiving ship reports after the transfer.

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 only 33%, and the description compensates by explaining the fit vs injured distinction that drives fit_crew/fit_marines/injured_crew/injured_marines, including capacity rules and the swap rule. It still leaves the individual count parameters' interaction (e.g. whether at least one must be nonzero, upper bounds) unstated.

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 (transfer) plus resource (fit/injured crew and marines) and scope (to an allied ship at the same POI). This clearly separates it from siblings like recruit_personnel, treat_personnel, and faction_personnel without needing the schema.

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 strong operational preconditions: both ships out of combat, donor must retain one fit crew member, and the target must be visible at the same POI. It does not explicitly name alternative tools for related tasks (e.g. treating injured personnel, recruiting), so it stops short of full when/when-not routing.

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