nasa_power_climatology

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

With no annotations, the description carries the burden and does well by disclosing the baseline period (2001-2020), the climatological nature (monthly/annual averages), single-point limitation, and the 'not a forecast' caveat. No contradictions.

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 tightly composed sentences: the first states the core functionality and baseline, the second adds use cases and a critical exclusion. No fluff or redundant phrases.

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 description covers the essential context: what data is returned (climatology for a point), the baseline, use cases, and what it isn't. It doesn't describe return format, but given the schema's parameter details and the tool's simplicity, it's adequate for an agent to select and invoke it correctly.

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 already covers descriptions for profile, community, and parameters (60% coverage). The description adds use-case context but doesn't clarify individual parameters beyond what the schema provides; latitude/longitude are self-explanatory. Adequate but not compensating beyond baseline.

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 retrieves NASA POWER monthly and annual climatology for a single latitude/longitude with a specific baseline (2001-2020). It distinguishes from daily or forecast tools via the 'not a forecast' note, making it highly specific.

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?

The description gives clear context: useful for typical weather, rainfall, wind, solar potential, and growing conditions, and explicitly excludes forecasts. It doesn't name alternative tools but the sibling nasa_power_daily is implied for daily data. No explicit alternatives, so not a 5.

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