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

With no annotations, the description must disclose behavioral traits. It only says 'current temperature' and doesn't mention that only the 'city' parameter is used, that other parameters are discarded, or any side effects/limitations. The schema hints at discarding but the description doesn't confirm or add context.

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?

It is a single concise sentence, but it is under-specified and lacks structure. It doesn't front-load any caveats or usage notes. Brevity is good but at the expense of necessary information.

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?

With 9 optional parameters, no output schema, and no annotations, the description is extremely incomplete. It doesn't explain what the tool returns, how it decides which parameter to use, or any behavioral details. An agent cannot correctly invoke this tool based on the description alone.

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 description coverage is 100% (all 9 parameters have descriptions), so the baseline is 3. The description adds no extra meaning beyond the schema; it doesn't clarify that only 'city' matters or explain the role of other parameters.

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 states a specific action ('current temperature for a city') but the input schema includes 9 unrelated parameters (ref, url, feed, json, path, zone, query, etc.) that suggest the tool does far more than weather. This creates confusion about the actual purpose and fails to differentiate from sibling tools like geo-hint or timezone.

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 alternatives. There is no mention of conditions, exclusions, or which sibling tool to prefer for other scenarios. An agent is left to infer usage, which is insufficient.

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