maritime_get_vessel

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

No annotations were provided, so the description bears full responsibility. It clearly describes the tool as a retrieval operation returning vessel details, with no mention of side effects or destructive actions. While it doesn't explicitly state 'read-only', the description implies it. Additional context on rate limits or auth would improve transparency.

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 for Args, Returns, and Tips. It is slightly verbose (e.g., 'Tips for LLMs' heading) but each sentence adds value. Could be tightened while retaining clarity.

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 must explain return values. It lists the fields included in the full vessel record and mentions JSON or text formats. Tips help integrate with other tools. Some detail about the structure of the record would enhance completeness, but it's adequate.

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%, so the description must compensate. It provides detailed explanations for both parameters: vessel_id as an identifier from search results, and output_mode with 'json' (default) or 'text'. This adds significant meaning beyond the bare 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?

The description explicitly states it 'Get full details for a specific vessel' and lists the fields returned (name, type, tonnage, etc.), clearly distinguishing it from search tools like maritime_search_vessels.

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 includes specific guidance: use maritime_search_vessels first to find vessel_id, and provides cross-references to maritime_get_hull_profile and maritime_search_voyages with context on when to use them. It also explains tonnage units.

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