Refresh Intraday

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

No annotations are provided, so the description carries the full behavioral burden. 'Refresh' implies some kind of re-fetch or update, but the description does not disclose whether it mutates stored data, whether it requires special permissions, whether it has rate limits, or what side effects may occur.

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 front-loaded sentence with no filler. It conveys the action, resource, scope, and intended caller context without wasting words.

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?

Although the tool is simple and has an output schema, the lack of usage guidance and behavioral disclosure leaves important context missing. An agent cannot confidently determine when to call this tool or what calling it actually does beyond the vague notion of refreshing intraday data.

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 needed to add meaning to the 'city' parameter. It only repeats the parameter name and adds no clarification about whether city is a name, ID, slug, or what format is expected.

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 clear action ('refresh'), a clear resource ('intraday readings'), and a scope ('for a city'). It is distinguishable from sibling refresh_* tools by data type, though 'readings' is slightly generic and could be more specific.

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?

There is no explicit when-to-use or when-not-to-use guidance. The parenthetical 'called from UI' hints at an intended invocation context, but it does not tell the agent how to choose this over refresh_forecast, refresh_conditions, or other refresh siblings, or whether direct agent invocation is appropriate.

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