Refresh Temperature

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Refresh' implies some kind of update or data-fetching side effect, but the description does not explain whether it mutates caches, makes network calls, is idempotent, or requires permissions. This is a meaningful gap for an action-oriented tool.

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 efficient sentence with no filler. The useful UI-context qualifier is included without bloating the text, and the core action/resource pair is front-loaded.

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?

While the tool is simple and an output schema exists, the description still omits essential context: what 'refresh' actually does, when to use this over sibling tools, and how the city parameter should be specified. With no annotations and 0% schema description coverage, this is incomplete for safe and correct invocation.

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 0%, so the description must compensate for the missing parameter documentation. It only says 'for a city,' which repeats the schema's parameter name and adds no format, identifier type, accepted values, or interpretation of the city field.

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 identifies a specific verb ('refresh') and object ('temperature data for a city'), and the parenthetical '(called from UI)' adds a useful contextual marker. It narrows the resource to temperature, which distinguishes it from many sibling tools, though it does not explicitly differentiate itself from get_current_temperature or refresh_conditions.

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 'called from UI' parenthetical implies this tool is intended for UI-triggered refreshes rather than general data fetching, which gives some usage context. However, it does not name alternatives, exclusion conditions, or when to prefer sibling tools like get_current_temperature, leaving the guidance mostly implied.

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