get_weather_by_location

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

No annotations are provided, and the description does not disclose behavioral traits such as what happens if no station is nearby, potential caching, rate limits, or side effects. The description only states the basic function.

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 a single, clear sentence that conveys the essential information without clutter. Every word is meaningful and earns its place.

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 well-defined parameters, the description provides the core purpose. However, it lacks usage guidelines and behavioral context for edge cases, leaving some gaps for an agent to fully understand when and how to invoke this 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?

The input schema already describes lat and lon with 100% coverage, but the description adds context that the tool uses these coordinates to find the nearest AMeDAS station, which explains the parameter purpose beyond the schema. This adds useful meaning.

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 verb 'Get', the resource 'current weather', and the method 'from the nearest AMeDAS station to given coordinates'. It effectively distinguishes from sibling tools like get_forecast or get_historical_weather by specifying 'current' and location-based retrieval via coordinates.

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 indicates when to use this tool (i.e., to get current weather from coordinates), but it does not provide guidance on when not to use it versus siblings like get_current_weather or search_nearby_stations. No alternatives or exclusion criteria are given.

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