get_current_weather

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

Describes the processing steps (extracting current hour's temperature, mapping weather code) and the return format. Without annotations, this provides adequate behavioral transparency.

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 lines, front-loaded with the core purpose, no waste. Efficiently communicates functionality.

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 simple one-parameter tool without output schema, the description covers the essential behavior and output format. Lacks details on error handling or unavailable cities, but acceptable.

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 tool description itself does not discuss the city parameter; the input schema's parameter description already provides full guidance (including translation note). Baseline 3 due to 100% schema coverage.

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?

Clearly states it gets current weather for a city and describes the output (temperature, weather code, summary). Differentiates from sibling tools like get_weather_details or get_weather_byDateTimeRange.

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?

Implies use for current weather but does not explicitly state when to use versus alternatives or provide exclusions (e.g., historical data, forecasts).

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