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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by enumerating the returned quantities (annual and monthly AC kWh, solar resource, capacity factor), which is genuinely useful given there is no output schema.

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 zero filler; the core capability and model version are front-loaded before the audience note. Nothing here repeats structured fields verbatim.

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?

For a stateless estimation endpoint with full schema coverage and annotations covering safety, the description is nearly complete, and the return-value summary compensates for the missing output schema. It stops short of mentioning the address-or-coordinates requirement, which is the main practical trap when calling it.

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% and all nine parameters are individually documented with units, defaults and enum-like mappings, so the schema does the heavy lifting. The description adds nothing about parameters — notably it omits that either address or lat+lon is required — so the baseline 3 applies.

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?

States a specific verb and resource ('Estimate solar PV system production') and names the underlying model (NREL PVWatts v8), which pins down exactly what the tool computes. It does not, however, differentiate itself from the sibling nrel_solar_resource, leaving the agent to infer the boundary between resource lookup and production estimation.

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 audience sentence ('used by solar developers, homeowners, and ESG analysts to size and estimate solar arrays') implies a sizing/estimation use case but gives no explicit when-to-use condition, no prerequisites (API key, address vs lat/lon), and never names an alternative such as nrel_solar_resource. Usage is only inferable.

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