maritime_get_timeline

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

No annotations provided, so description carries full burden. It reveals that events combine multiple archives, may have conflicting dates, that include_positions can add many events, and that output includes geojson LineString. Nearly comprehensive, though lacks mention of read-only nature.

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?

Well-structured with headings (first sentence, paragraph, Args, Returns, Tips for LLMs). Approximately 150 words, no redundancy. Could be slightly more compact, but is clear and organized.

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?

Covers purpose, usage, parameters, output format, and data sources. Tips provide practical advice. Lacks error handling details or ordering criteria, but overall complete for a complex tool with no output schema.

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%, but description compensates fully with an Args section explaining each parameter: voyage_id with example, include_positions with default and effect, max_positions with default, output_mode with format options.

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 starts with 'Build a chronological timeline of events for a voyage.' which is a specific verb+resource. It distinguishes from sibling 'maritime_get_voyage_full' by stating it returns non-chronological linked data.

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 when-to-use (chronological timeline) and when-not (non-chronological linked data). Tips for LLMs offer practical usage guidance: start with include_positions=False, then set True for detailed track.

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