search_listings

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

No annotations are provided, so the description carries the full burden. It only states that it searches and filters, but does not disclose behavioral traits such as default limits, pagination, or what 'etc.' includes. This is insufficient for a tool with no other behavioral information.

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 a single concise sentence, but it uses a vague 'etc.' and omits a structured breakdown of filter options. It is efficient, with no wasted words, but could be slightly more informative.

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?

The tool has 14 parameters and no output schema or annotations. The description provides only a high-level purpose, failing to clarify output format, search behavior, or limitations. Given the complexity, this description is insufficient for a complete understanding.

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 93%, with detailed descriptions for most parameters (e.g., 'city', 'limit', 'min_price'). The description's mention of 'city, price, bedrooms, property type' adds no new semantic detail beyond the schema.

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 uses the specific verb 'search' and identifies the resource as 'real estate listings in Paraguay', clearly distinguishing it from sibling tools like search_projects and get_listing. It also lists some filter options, providing a clear understanding of the tool's function.

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 provides clear context for searching real estate listings in Paraguay, but does not explicitly state when to use this tool over alternatives or when not to use it. Usage is implied from the purpose, but no exclusions or alternative tools are mentioned.

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