ocean_sea_ice

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

The description is very brief and does not disclose any behavioral traits (e.g., read-only, authentication needs, rate limits, or data freshness). Since no annotations are provided, the description carries the full burden, which it fails to meet.

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 very concise, with one sentence covering the core purpose. It wastes no words, but could be slightly more front-loaded with a verb. Overall, efficient.

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?

The tool has no output schema and a simple input, so the description should explain what the output includes (e.g., time series, area, maps). It only says 'reference', which is vague. An agent cannot determine what kind of data to expect.

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 100%, with one parameter 'region' described as 'Polar region'. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the tool provides 'Sea ice extent information' for Arctic and Antarctic, which is a specific data resource. It distinguishes from sibling tools like ocean_buoy_data or ocean_sst_anomaly. However, it lacks a verb like 'retrieve' or 'get', which slightly reduces precision.

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?

No guidance on when to use this tool versus other ocean or sea-ice related tools (e.g., env_ocean_temp). No when-not or alternative suggestions are provided, leaving the agent to infer usage context.

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