get_sale_listings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it 'Returns a list of sale listings', missing critical details like whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior (implied by 'page' and 'page_size' parameters but not explained), or error handling. This is insufficient for a tool with 13 parameters and no output schema.

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?

The description is concise with two short sentences that are front-loaded, stating the purpose and return value efficiently. However, it's overly brief given the tool's complexity, bordering on under-specification rather than optimal conciseness.

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 the high complexity (13 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain the filtering logic, return format, pagination, or behavioral traits, making it inadequate for an agent to use this tool effectively without additional context or 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%, meaning none of the 13 parameters have descriptions in the schema. The description only vaguely mentions 'various filters' without explaining what those filters are (e.g., zip_code, price ranges) or how they interact. It fails to compensate for the lack of schema documentation, leaving parameters largely unexplained.

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 states the tool 'Get sale listings with various filters' which provides a basic verb+resource combination, but it's vague about what 'sale listings' specifically entails (e.g., real estate properties) and doesn't distinguish it from sibling tools like 'get_property_listings' or 'get_sale_listing_by_id'. It's adequate but lacks specificity and differentiation.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'get_sale_listing_by_id' for single listings or 'get_property_listings' for broader property searches, nor does it specify prerequisites or exclusions. This leaves the agent without context for tool selection.

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