get_weather_by_position

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

With no annotations, description carries full burden. It discloses return structure (dict with 'data' and '_meta') and error behavior (MCPError). However, it omits details like rate limits, auth requirements, destructive potential, and caching behavior.

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?

Description is concise and front-loaded with purpose. Uses structured docstring format but could be more terse by omitting the Python-style 'Args:' and 'Returns:' boilerplate.

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?

Covers input, return structure, and errors. However, lacks examples, constraints, and usage context. For a 3-parameter tool with no output schema, it is minimally adequate but not rich.

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 0% so description must compensate. It names parameters (lat, lon, provider) with brief definitions but lacks details like decimal degree ranges, coordinate system, or the meaning of provider options beyond a list.

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 it retrieves comprehensive weather (current, hourly, daily) by latitude/longitude. It distinguishes from sibling tool get_weather_by_name which uses location names.

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 versus siblings (e.g., get_weather_by_name). The provider parameter is listed but no advice on selecting among 'all', 'qweather', etc. No when-not or alternative directions.

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