get_rental_listings

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, how results are ordered, pagination behavior (despite page/page_size parameters), rate limits, authentication requirements, or data freshness. 'Returns a list' is the only behavioral detail.

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 zero waste, but under-specified. The first sentence introduces the tool, the second states the return type. However, for a tool with 13 parameters and no annotations, this brevity comes at the cost of completeness.

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 complex tool with 13 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the return structure, error conditions, or how to interpret results. The agent would struggle to use this effectively without trial and error.

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% (titles only, no descriptions), and the description doesn't compensate. It mentions 'various filters' but doesn't explain what filters are available, how they combine (AND/OR logic), or provide examples. With 13 undocumented parameters, this leaves significant gaps in understanding.

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 verb ('Get') and resource ('rental listings'), specifying it returns a list. It distinguishes from siblings like get_property_listings by focusing on rentals, but doesn't explicitly contrast with get_rental_listing_by_id or other rental-specific tools.

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 get_rental_listing_by_id (for single listings) or get_property_listings (which might include sales). The description mentions 'various filters' but doesn't explain when filtering is appropriate versus using other tools.

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