search_listings

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds behavioral traits: returns one page of summaries, includes specific fields, and notes that sponsored ads may not match all filters. This exceeds what annotations provide without contradiction.

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 four sentences, each adding essential information. It front-loads the purpose and resource, then details returns, directs to a sibling tool, and clarifies a special case. No superfluous content.

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 full schema coverage, annotations, and presence of an output schema, the description provides sufficient context. It explains core functionality, return fields, and a special behavior (sponsored ads), making the tool easy to use correctly.

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 coverage is 100% with descriptions for each parameter. The description adds meaning by stating that price is in euros/month and surface in m², and explains how sponsored ads behave, which aids in understanding the output beyond the raw 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 clearly states the verb 'search' and the resource 'rental listings on Kamernet.nl'. It specifies what is returned (price, surface, availability, URL) and distinguishes from the sibling tool get_listing by instructing to use it for full details.

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 explains that for full listing details one should use get_listing, and notes that sponsored top ads are returned separately. While it does not explicitly state when not to use this tool or mention get_new_listings, it provides useful context for selecting between tools.

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