Refresh Forecast

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'refresh forecast data.' It does not explain whether this mutates cached data, whether it is idempotent, what side effects occur, or what permissions/rate limits apply. The UI parenthetical is the only extra behavioral hint.

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 with no filler, and the core action is front-loaded. It is concise, though the parenthetical could have been used more effectively to convey usage guidance rather than just UI provenance.

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 absence of annotations and the sparse description, the agent has no way to know what a 'refresh' entails or when it should choose this over a view/get sibling. The output schema covers return values, but behavioral and usage context remains incomplete.

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 schema has zero description coverage for the 'city' parameter, and the description only says 'for a city,' which largely restates the parameter name without adding format, expected values, or examples. It does not compensate for the missing schema documentation.

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 and resource: 'Refresh forecast data for a city.' The parenthetical '(called from UI)' adds context, but it does not explicitly distinguish this tool from siblings like get_forecasts or forecast_view. It is clear enough to be understood, but sibling differentiation is left implicit.

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 is given on when to call this tool versus the many sibling view/get tools. The phrase 'called from UI' implies it may be intended for UI-triggered refresh actions, but it does not state alternatives, exclusions, or conditions for agent use.

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