get_new_listings

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

With no annotations, the description carries full behavioral disclosure burden. It mentions the core behavior (first observed since a time, newest first), which implies a read-only query, but it does not discuss pagination, auth needs, rate limits, or whether only active listings are returned. It is adequate but not rich.

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?

A single, tight sentence with no redundancy. It front-loads the essential behavior ('first observed since a given time') and adds the sort order ('newest first'), earning its place without 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?

Given the tool has 12 parameters, zero annotations, and many sibling query tools, this one-sentence description is too thin. It does not explain how filters interact, what 'first observed' means operationally, or how this differs from similar search/list tools, so an agent may struggle to invoke it 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 only 50% (6 of 12 parameters have descriptions), and the tool description adds no parameter meaning at all. Undocumented parameters like make, model, keywords, price_max, seller_type, and transmission remain without clarification, so the description does not compensate for the schema gap.

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 returns listings first observed since a given time, sorted newest first. It effectively distinguishes from siblings like search_cars and get_listing_changes through the 'first observed' concept, though it doesn't explicitly name alternatives.

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?

No guidance is given on when to use this tool versus siblings such as search_cars, find_deals, or get_listing_changes. The appropriate context is only implied by the name and one-line description, with no explicit 'use this when...' or 'not for...' direction.

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