maritime_get_muster

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

No annotations provided, so description carries full burden. Describes returned data fields (ranks_summary, total_european, etc.) and output modes, but lacks error handling or prerequisite details. Overall good behavioral disclosure.

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?

Description is well-organized with sections (summary, details, Args, Returns, Tips) but slightly verbose. Every sentence adds value, though 'Tips for LLMs' could be integrated into main 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?

Given no output schema and sibling tools (search_musters, get_voyage, etc.), description covers what is returned, how to use, and related actions. Lacks mention of error handling or edge cases, but sufficient for a get-by-id tool.

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 0%, but description adds meaning: gives an example for muster_id ('dss_muster:0001') and explains output_mode default. Compensates well for missing schema 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?

Description clearly states 'Get full details for a specific ship muster record.' and distinguishes from sibling tools like maritime_search_musters, which are used to find the muster_id first.

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?

Provides explicit tips: use maritime_search_musters to find muster_id, compares with maritime_search_crew for related data, and suggests using maritime_get_voyage if das_voyage_id is set. Clearly tells when to use alternatives.

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