get_new_listings

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

Discloses sorting by newest, client-side filtering, statelessness, and politeness constraints. Annotations already indicate readOnly and openWorld, and description adds valuable behavioral context beyond those.

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?

Four sentences, all essential. First sentence states purpose, subsequent sentences add guidance and detail. No wasted words.

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?

Description covers the core use case well. Annotations confirm safety and open-world nature, and output schema exists. Minor gaps: no mention of optional filters like max_rent, but overall adequate.

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 50% with descriptions for 3 of 6 parameters (city, since, radius_km). The description does not add further parameter details, so it meets a baseline but does not compensate for missing schema descriptions.

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 tool checks for new listings since a given timestamp for stateless monitoring. It distinguishes from siblings (get_listing, search_listings) by focusing on incremental updates.

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?

Explicitly advises polling periodically, remembering the timestamp, and not polling more than every few minutes. Provides clear usage context without needing to reference alternatives.

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