Marine Weather

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

Adds value beyond annotations by detailing data returned, date constraints (max 16 days, current/future only), and coordinate recommendation. Does not address rate limits or behavior with multiple identifiers, but covers key behavioral aspects.

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?

Four clear, front-loaded sentences with no superfluous information. Every sentence provides essential guidance, making it efficient for an AI agent to parse.

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 core usage patterns and return data despite no output schema. Mentions wave, swell, wind, sea-surface. Lacks detail on edge cases (e.g., missing identifier) and timezone behavior, but adequate for most use cases.

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?

Adds significant context beyond schema descriptions: outlines the real-time vs forecast mode logic, recommends coordinates for marine, and states 'at least one of location/lat+long/ip' requirement. The schema itself has 100% description coverage, but the description provides higher-level usage semantics.

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?

Clearly states it retrieves marine/ocean weather in real-time or forecast up to 16 days, specifying return data (wave height, swell, wind, sea-surface). Differentiates from land-based weather tools (e.g., weather_forecast) via 'marine' focus.

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?

Explicitly provides conditional logic for real-time vs forecast (omit dates vs provide start/end), recommends coordinates for offshore queries, and requires at least one identifier. Lacks explicit comparison to sibling tools but context is clear.

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