Refresh Flow

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'refresh' and offers no details about side effects, idempotency, cache invalidation, authentication, or rate limits. This is a significant gap for a tool that mutates or refreshes data.

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 very short and front-loaded, with minimal filler. The parenthetical '(called from UI)' is only marginally useful and could be removed, but overall the text is appropriately concise.

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?

The input schema is simple and an output schema exists, but the description omits what a refresh actually changes and whether repeated calls are safe. Given no annotations and a large family of similar refresh tools, this is not enough for confident 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%, and the description adds only 'for a city,' which largely restates the city parameter. It confirms city-scoped behavior but provides no additional format, constraints, or examples.

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 flow and safety data for a city.' This identifies the operation and the target data. It does not explicitly distinguish it from the sibling refresh_safety, but the combined resource scope is reasonably clear.

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 only usage signal is '(called from UI)', which does not explain when an agent should choose this tool over the many sibling refresh_* tools. There are no conditions, exclusions, or alternatives such as refresh_safety or flow_card.

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