weather_by_coords

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

With no annotations, the description must disclose behavioral traits. It only states 'current weather plus a short forecast' without explaining what 'short' means, forecast duration, or data sources. Important traits like clamping of days parameter are absent, requiring the agent to infer from the 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?

The description is extremely concise (8 words), front-loading the core purpose. While effective, it could include a bit more context (e.g., forecast range) without harming conciseness.

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 the presence of an output schema and low tool complexity, the description is minimally adequate. It lacks details about forecast duration and parameter usage, but the schema compensates partially.

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 coverage is 100%, and the description adds no parameter-specific meaning beyond what the schema already provides. The description's mention of 'any latitude/longitude' echoes the schema, providing no additional value.

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 explicitly states the tool provides 'current weather plus a short forecast' for any lat/lon, using specific verbs and a clear resource. It inherently distinguishes from sibling tools like uae_weather and air_quality_by_coords by emphasizing coordinate-based, general weather data.

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 on when to use this tool over alternatives such as uae_weather or uae_weather_forecast. The description does not mention exclusions, prerequisites, or typical use cases, leaving the agent without decision support.

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