refresh_prices

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

With no annotations, the description fully discloses behavior: it bypasses the CDN cache, hits poe.ninja origin, does not touch GGG's trade API, and thus cannot affect the player's in-game trade rate budget. This is exactly the kind of context an agent needs for a mutating-like operation.

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?

Three short paragraphs, each adding value: core purpose, technical nuance with usage conditions, and safety/caveat. Front-loaded with the main action, no redundant phrasing.

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?

Behavioral context is thorough, but the league parameter is completely undocumented, which is a significant omission for a tool that likely needs to know which league's prices to refresh. The output schema exists, so return format is not needed, but parameter documentation is essential.

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 one optional parameter 'league' with 0% description coverage, and the description never mentions it. The agent is left to guess what league values are acceptable or whether it's required for the refresh. This is a clear gap.

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 states it fetches currency prices from poe.ninja immediately, bypassing the schedule. It distinguishes itself from the hourly sweep and implies it's a refresh operation, differentiating it from sibling tools like get_price or get_movers which fetch or analyze data rather than force-refreshing.

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?

Explicitly states when to call: when stale:true appears or after sleep/offline. Also warns that a forced refetch may not yield different data, setting expectations. It doesn't name alternatives but the contrast with the hourly sweep implies when not to use it.

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