refuge_infoDatos generales del Refugio San Bernardo (Vallecitos, Cordón del Plata, Mendoza, 2.800 m): ubicación, altitud, tipos de habitación, horarios y política de seña. Usar cuando se hable de Vallecitos, Cordón del Plata, Cerro El Plata, aclimatación para el Aconcagua, o trekking/andinismo en Mendoza.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true. Description adds value by specifying the exact information returned (location, altitude, room types, etc.) and that it's general data, but doesn't detail the return format.
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?
Single sentence that front-loads key info (refuge name, location, altitude) and includes usage guidance. No wasted 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?
For a read-only info tool with no parameters and no output schema, the description adequately covers what the tool does and when to use it. The listed data categories provide sufficient context.
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 parameters in schema (100% coverage). Description doesn't need to explain params; it adds meaning by describing what the tool returns, meeting the baseline for zero-parameter tools.
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 the tool provides general data about Refugio San Bernardo, including location, altitude, room types, hours, and policy. Distinguished from sibling tools like check_availability or get_price by focusing on overall info.
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 lists when to use (when talking about Vallecitos, Cordón del Plata, Cerro El Plata, acclimatization, etc.), providing clear context and implicitly differentiating from more specific tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose covering availability, closures, contact, pricing, weather, directions, room types, general info, and reservations. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., check_availability, get_price, list_room_types, request_reservation). 'how_to_arrive' is the only slight deviation but still clear.
9 tools is well-scoped for a mountain refuge information and booking system. Each tool earns its place without being excessive or insufficient.
Covers the full user journey: information, availability, pricing, weather, directions, and reservation request with preview/confirm. Missing cancellation or reservation status check, but these are not critical for the core workflow.