Search Huts

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the safety profile is clear. The description adds value by revealing it searches 'cached' data and does not call a geocoder, which impacts latency and data freshness. 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 with no unnecessary words. The first sentence states the core functionality; the second adds a critical behavioral caveat. Every part earns its place, and the structure is front-loaded with the primary purpose.

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 6 parameters, nested objects, and no output schema, the description is incomplete. It does not mention the output format (e.g., list of huts), pagination behavior (limit/offset), or constraints like max radius. The tool is moderately complex, and the description leaves significant gaps for an agent to handle correctly.

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%, so the description must compensate. It explains the purpose of 4 out of 6 parameters (country, canton, text, near) but omits limit and offset. It adds some meaning beyond the schema (e.g., 'canton cache' for canton, 'distance around coordinates' for near), but does not fully cover all parameters.

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 tool searches cached huts using specific filters (country, canton, text, distance), providing a specific verb and resource. It also notes the tool does not use a geocoder, adding extra clarity. The purpose is well-differentiated from sibling tools like search_hut_availability.

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 versus alternatives like search_hut_availability or list_bookings. The description lacks usage context, exclusions, or suggestions for when this tool is preferred. An agent would need to infer usage based solely on the tool name.

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