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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds that the profile is 'canonical' and multi-model and that seasonal detail is optional, but omits precedence rules when both fingerprint and coordinates are supplied and says nothing about behavior when neither identifier is given.

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, front-loaded with the resource and metrics, with the optional-detail caveat trailing. No redundant restatement of the name or filler.

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 4-parameter read tool with no output schema and only standard annotations, the description covers what is returned and the two lookup modes but leaves the parameter interplay (lat/lon pairing, fingerprint precedence, behavior on missing identifiers) unresolved, which an agent needs to call 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 description coverage is 0%, so the description must compensate; it loosely maps all four parameters ('by fingerprint or coordinates' covers fingerprint_key/lat/lon, 'full seasonal detail is optional' covers include_seasons). However it does not state that lat and lon must be supplied together, the format of fingerprint_key, or which input wins when both are provided.

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 ('Read') on a specific resource ('canonical multi-model chill profile') and enumerates the three metrics returned (Chill Hours, Utah Units, Dynamic Chill Portions), which distinguishes it from generic siblings like abiyar_location_profile and abiyar_assess_suitability. The two lookup modes (fingerprint or coordinates) are also named.

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 implies the two ways to call it and that seasonal detail is optional, but never says when to prefer it over abiyar_location_profile or abiyar_assess_suitability, nor when fingerprint should be used instead of coordinates. Usage is only implied, not stated.

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