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

With no annotations, the description partially covers behavioral traits: it indicates a read operation returning UV Index and burn times, but lacks details on data source, latency, rate limits, or response structure. No contradictions with annotations (none exist).

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?

Single sentence, front-loaded with the main action, no extraneous words. Meets conciseness standards perfectly.

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?

Given no output schema and simple schema, the description is too sparse. It omits output format, UV Index scale (e.g., 0-11+), unit for burn times, and whether data is real-time or forecasted, making it insufficient for confident invocation.

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?

Description provides zero parameter context. Schema coverage is 0%, and the description does not mention lat or lng, their meaning, constraints, or format, leaving the agent with only schema examples.

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 uses specific verbs 'retrieves' and 'calculates', clearly identifying the tool's dual function of fetching UV Index data and computing burn times, distinguishing it from weather-related siblings like getAirQuality or getPollenCount.

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 is provided on when to use this tool versus alternatives (e.g., getAirQuality, getWeatherAnomaly). There is no mention of prerequisites, geographical scope, or data freshness preferences.

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