Refresh Weather

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'refresh weather data' without explaining side effects, whether it mutates state, requires auth, is idempotent, or what happens after the call. The verb 'refresh' implies a state change but no details are given.

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 short sentence, which is appropriately sized for a one-parameter tool. It front-loads the action and resource, though the parenthetical 'called from UI' is somewhat extraneous and unclear, but it does not bloat the 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?

Despite having an output schema, the description leaves crucial behavioral aspects unexplained. For a tool with no annotations, it fails to clarify the purpose beyond 'refresh', making it incomplete for an agent to decide when and how to use it correctly.

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 the description must compensate for the undocumented 'city' parameter. It only mentions 'for a city' without specifying whether it expects a name, ID, coordinates, or any format. This adds minimal meaning beyond the schema's type declaration.

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 (refresh) and resource (weather data for a city), which is clear enough on its own. However, it does not differentiate from sibling refresh tools like refresh_conditions or refresh_forecast, leaving ambiguity about which specific weather data is refreshed.

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 phrase 'called from UI' is the only usage hint, but it does not explain when an agent should call this tool versus alternatives like refresh_conditions or refresh_forecast. There is no clear guidance on conditions or exclusions.

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