maritime_get_crew_member

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

No annotations provided, but the description compensates by listing returned fields (name, rank, origin, etc.), explaining pay units (guilders) and meaning of fate values (survived, died_voyage, etc.). It does not mention side effects, but as a read operation, it is adequately transparent.

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 well-structured with sections and front-loaded purpose, but includes some repetition (e.g., listing fields in both the initial sentence and the return explanation). Every sentence adds value, but could be slightly more compact.

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 simple 2-parameter tool with no output schema, the description covers all aspects: parameters, return data fields, units, and cross-reference suggestions. It is fully self-contained for the agent to use effectively.

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 0%, yet the description adds full meaning: crew_id is 'Crew member identifier (from search results)' and output_mode options are explained ('json' or 'text'). It also provides domain knowledge about pay and fate constants, far exceeding baseline.

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 clearly states 'Get full details for a specific crew member' with a specific verb and resource. It distinguishes itself from sibling tools like maritime_search_crew which is for finding IDs, and other 'get' tools by focusing on crew members.

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?

Explicitly instructs to use maritime_search_crew first to obtain crew_id, and suggests cross-referencing with maritime_get_voyage for full context. It also explains the output_mode parameter options, providing clear when-to-use guidance.

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