Arctic Sea Ice Extent

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

Adds value beyond annotations by specifying data source (NSIDC), frequency (monthly), default lookback (10 years), and units. Annotations already indicate read-only and idempotent; description complements well.

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?

Two sentences with essential information, no extraneous words. Front-loaded with key details: data source, unit, time range.

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?

Sufficient for a simple read-only data retrieval tool with one optional parameter. Covers source, units, default, and temporal scope. Output schema likely covers return fields, so description is adequate.

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 100%, and the description reiterates the default behavior ('returns last 10 years by default') which is already implied by the schema. No additional parameter meaning beyond 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?

Clearly states it returns arctic sea ice extent measurements from NSIDC, with units and time range. Distinguishes from sibling climate indicators like CO2 and temperature by specifying 'Arctic sea ice extent'.

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?

Implies usage for tracking Arctic ice decline but does not explicitly state when to use this tool over alternatives or when not to use it. Context is provided but no exclusion criteria.

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