Refresh Hut Catalog

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

Description adds context beyond annotations: explains upstream calls are read-only and local cache mutation. This clarifies the read-only annotation false (mutation is local). No contradictions with annotations.

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 sentences, each earning its place: first states action, second clarifies behavioral boundaries. No unnecessary 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?

Adequate for a simple refresh operation but lacks mention of prerequisites (e.g., network access), error handling, or connection to sibling tools (e.g., search_huts depends on this cache). With no output schema, impacts of failures are unclear.

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?

Description provides no information about the two parameters (country, limit) beyond what's in the schema, which has 0% coverage. Agent must infer meaning from names alone, which could be ambiguous (e.g., country format).

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?

Description clearly states it fetches hut list and details from hut-reservation.org into local cache, distinguishing it from sibling tools like refresh_area_cache (different resource) and search_huts (query vs refresh). The verb 'refresh' and resource 'hut catalog' are 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?

Description implies usage for refreshing local cache but lacks explicit guidance on when to use vs alternatives (e.g., search_huts for queries) or prerequisites. No mention of context like 'call before searching for availability'.

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