Bulk Current Weather

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

Annotations already declare readOnlyHint=true, idempotentHint=true, removing need for safety caveats. The description adds that it returns weather+astronomy data wrapped in a 'bulk' array, which is valuable behavioral context beyond 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?

Two sentences, front-loaded with the core function. Every word adds value: 'real-time', 'up to 50 locations', 'city name, lat/long pair, or IP address', 'returns weather + astronomy data'. No wasted text.

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 read-only bulk query tool with one parameter and comprehensive annotations, the description covers the input constraints (max 50, location options), the output format (weather+astronomy in bulk array), and the data type. No output schema exists, but the description sufficiently informs the agent.

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 provides thorough descriptions for each property (100% coverage). The description adds an example showing mixed location types, which helps clarify usage, justifying a slight bonus above baseline 3.

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 'real-time weather', and the key differentiator 'for up to 50 locations at once'. It distinguishes itself from sibling 'weather_current' by emphasizing bulk capability.

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 the allowed location formats (city name, lat/long, IP) and gives an example, but does not explicitly state when to use this tool versus alternatives like 'weather_current' for single locations. However, the bulk implication is clear.

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