listar_propiedades

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

No annotations are provided, so the description carries the burden. It discloses pagination behavior but does not mention authentication requirements, rate limits, or whether the operation is read-only (though implied by 'lista'). The description is straightforward but lacks deeper behavioral context.

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, well-structured sentence that delivers the core purpose upfront: listing with filters and pagination. No superfluous 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?

Given no output schema, the description omits what the returned results contain (e.g., property IDs, names, pricing). It covers filtering and pagination but lacks completeness about the response structure, which is important for an agent to interpret tool output.

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 input schema has 100% description coverage, so baseline is 3. The description adds value by grouping parameters conceptually (location, capacity, features) and mentioning pagination, which provides meaning beyond the individual parameter descriptions.

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 lists all available vacation properties with optional filters by location, capacity, and features, and includes pagination. It distinguishes from sibling tools like 'buscar_disponibilidad' and 'calcular_precio_estancia' by focusing on listing all properties rather than specific queries.

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?

The description implicitly indicates usage for broad property listing with filters and pagination, but does not explicitly state when to use this tool versus alternatives like 'buscar_disponibilidad' or 'obtener_detalles_propiedad'. No exclusions or when-not-to-use guidance is provided.

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