weather_us

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

Reveals cost ($0.003/call), caching up to 10 minutes, shared cache for nearby coordinates, and public domain data. No annotations provided so description carries full burden; these disclosures are valuable.

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?

Three sentences, front-loaded with cost and purpose. Every sentence adds value; no redundancy.

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?

Explains return values (temperature, wind, forecast text, place name) despite no output schema. Also covers caching, cost, and coverage boundaries. Could mention units but complete enough for a simple tool.

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?

Input schema has 100% coverage with descriptions for lat/lon. Description adds context that coordinates must be US-based but does not add detail beyond schema. Baseline 3 is appropriate.

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?

Describes getting official US NWS forecast for coordinates, specifying output includes next four periods with temperature, wind, and detailed text. Clearly distinguishes from sibling tools (none weather-related).

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?

States usage for logistics, travel, event-planning. Explicitly notes US-only coverage and that non-US points return 404. No alternative tools mentioned but sibling list shows no weather tools.

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