Search StreetEasy rentals

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

No annotations provided, so description carries full burden. It discloses the return structure (compact list, totalCount, pagination, image URLs, url) and the read-only nature implicitly. Lacks explicit statements about auth or rate limits, but sufficient for a search tool.

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 paragraph with no fluff. Every sentence adds necessary information: purpose, area/amenity inputs, pagination, output fields. Front-loaded with main purpose.

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 14 parameters with full schema coverage and no output schema, the description adequately covers the tool's functionality: filters, valid inputs via sibling tools, pagination, and key output fields. Complete for a search tool 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?

Schema description coverage is 100%, but the description adds value by clarifying areas accept names or numeric codes, amenities are uppercase enum tokens, and directs to sibling tools for valid values. Also explains pagination parameters and output fields.

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 it searches active NYC rental listings with filters. It distinguishes itself from siblings (get_rental_details, list_amenities, list_areas) by specifying the search and filter functionality.

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?

Provides guidance on using list_areas and list_amenities to discover valid inputs, and explains pagination. However, it does not explicitly state when not to use this tool or provide exclusion criteria.

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