maritime_compute_track_speeds

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

Describes the algorithm (haversine distance, speed in km/day), default filters (min_speed=5, max_speed=400), and typical speed ranges for sailing ships. No annotations provided, but description adequately informs behavior, though could explicitly state 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 clear sections: overview, Args, Returns, Tips. Informative but slightly lengthy; every sentence adds value, though some redundancy could be trimmed.

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 parameter semantics, algorithm, output format, and usage tips. Lacks explanation of error handling or edge cases, but sufficient for a computation 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 coverage is 0%, but description includes a detailed 'Args' section explaining each parameter's meaning, defaults, and constraints (e.g., 'min_speed_km_day: filters out anchored/drifting'). Adds significant value 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?

Description clearly states it 'Compute daily sailing speeds for a single CLIWOC voyage' using haversine distance, distinguishing from sibling 'maritime_aggregate_track_speeds' for bulk analysis.

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 guidance: 'Get voyage_id from maritime_search_tracks results', 'Use lat/lon bounds to focus on a specific ocean region', and mentions alternative 'maritime_aggregate_track_speeds for bulk analysis'.

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