List properties

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

No annotations exist, so the description carries the full burden. It usefully discloses that include_live triggers an external Smoobu /api/apartments call and that the result set is fixed at 14 properties, but says nothing about read-only safety, permissions, or response shape for a tool whose safety profile is undocumented.

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?

Three short sentences with no filler; the return contents are front-loaded and the include_live behavior is appended where it belongs. The telegraphic style is dense but readable.

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, zero-required-parameter list tool with a fully documented schema and no output schema, the description supplies enough: what is returned, how filtering works, and the one parameter with a side effect. Only the absence of any read-only/permission framing leaves a small 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?

Schema description coverage is 100%, so the schema already documents all three parameters, and the description largely restates the enum values verbatim. The one genuinely additive detail is the domain mapping 'Casa 4 Modern = PERLA', which helps interpret the entity values.

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?

States a specific verb+resource (list the 14 properties) and enumerates the returned fields (Smoobu id, name, EOM entity, fiscal company/bsides account). It is clearly distinguishable from booking-oriented siblings like get_bookings and stays_in_month, though it never names an alternative explicitly.

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?

Usage is only implied: filter with entity/company, and set include_live to reconcile unmapped live apartments. There is no statement of when this tool is preferred over a sibling, no prerequisites, and no exclusions.

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