Ver detalle de una propiedad

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

Without annotations, the description carries the full burden. It clearly states it's a read operation returning property details. No contradictions. It could mention error handling (e.g., if ID not found) or authentication, but for a simple read tool, this is sufficient.

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?

A single sentence in Spanish, no wasted words. Front-loaded with the main action and purpose. Perfectly concise for the complexity of the tool.

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?

Given no output schema, the description outlines what the result includes (description, amenities, host). For a one-parameter read tool, this is adequate. Could detail response language or missing ID behavior, but the tool's simplicity limits the gap.

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 100% coverage for the single parameter 'id'. The description adds context: 'dado su ID numérico' and the schema description ties it to 'search_listings'. This adds meaning beyond raw type/description, linking the parameter to its source.

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 uses a specific verb ('Devuelve') and resource ('ficha completa de una propiedad del catálogo'), listing included fields ('descripción, amenities, anfitrión') and condition ('dado su ID numérico'). This clearly distinguishes it from sibling tools like 'search_listings' which returns lists.

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?

Explicit usage context: 'Usala para responder preguntas puntuales sobre una propiedad que ya apareció en una búsqueda previa'. This tells the agent when to use this tool (after a search) and implies not to use for initial searches. It also references the sibling 'search_listings' for the ID source.

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