Refresh Area Cache

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

The description adds the behavioral trait that it requires explicit geocoder configuration, which is beyond the annotations. However, it doesn't disclose mutation details or error states, though annotations already indicate non-read-only.

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?

Two concise sentences with no filler. Every word adds value. Front-loaded with the core action.

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?

With two parameters and no output schema, the description should compensate but only provides a high-level purpose and a prerequisite. Missing parameter docs and return value explanation make it incomplete for effective tool use.

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?

No description coverage in the schema (0%) and the tool description does not explain the meaning of 'force' or 'limit' parameters. Agents cannot infer correct usage from the description alone.

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 the action (reverse-geocode), resource (cached hut coordinates), and context (through Nomination-compatible provider). It distinguishes from siblings like refresh_hut_catalog which updates a different resource.

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 on when to use this tool vs alternatives like refresh_hut_catalog. Only mentions a prerequisite (explicit geocoder configuration) but no usage context or exclusions.

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