maritime_get_track

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

No annotations provided, so description carries full burden. It explains return structure (dated lat/lon positions daily), data nature (logbook readings, gaps), and accuracy (±20-50km). Does not explicitly state read-only, but 'get' implies it.

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-structured with sections, concise yet informative. Every sentence adds value, including tips for LLMs.

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 2 parameters and no output schema, description covers return type, data frequency, and accuracy. Could mention if dates are included explicitly, but 'dated lat/lon positions' suffices.

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 explains voyage_id as integer from search results and output_mode with default and options, adding meaning 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?

Description uses specific verb 'Get' and resource 'full position history for a CLIWOC voyage', clearly distinguishing from sibling tools like maritime_search_tracks and maritime_export_geojson.

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 clear usage context via tips: get voyage_id from search, positions are daily, gaps indicate missing entries, combine with export. Lacks explicit when-not-to-use but covers prerequisites and application.

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