get_weather

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

Without annotations, the description adequately explains the tool's behavior: it uses free APIs and geocoding, and lists the returned data. It does not disclose potential latency or rate limits, but the core transparency is sufficient.

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 with no wasted words, front-loads the purpose, and uses clear structure with separate sections for description and parameters.

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 that an output schema exists, the description sufficiently covers what the tool returns. It lacks mention of units or error handling, but for a simple tool, it is largely complete.

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?

The input schema has 0% coverage, but the description adds a clear parameter explanation with an example ('London'), which compensates beyond the schema's minimal 'City' title.

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 clearly states the tool retrieves current weather for any city, specifying the data sources and output fields. It implicitly distinguishes from forecast tools by mentioning 'current weather', but does not explicitly differentiate from siblings like 'get_forecast'.

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 explains when to use the tool (get current weather for a city) and what it does, but provides no guidance on when not to use it or which alternative tools (e.g., 'get_forecast', 'get_air_quality') might be more appropriate.

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