search_listings

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

No annotations provided. Description implies read-only search behavior but does not explicitly state safety, auth needs, or rate limits. Action of returning a limited set of fields is disclosed.

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?

Two sentences, no waste. First sentence states purpose and sources, second lists key return fields and directs to sibling. Front-loaded and efficient.

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?

With 2 parameters fully documented in schema, an output schema present, and a description that explains return fields and usage context, the tool is well-defined. Missing minor details like pagination ordering but sufficient for decision.

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 100%, so baseline is 3. Description adds minimal extra context by specifying free-text search accepts brand/model/reference, but does not significantly enhance schema meaning.

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?

Clearly states the verb 'Search/browse' and the resource 'WatchCharts Marketplace listings' with explicit sources (dealers, Reddit, forums, eBay). Distinguished from sibling get_listing by noting it returns summary info.

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 says returns summary fields and directs to use get_listing for full details, providing clear context for when to switch. However, lacks explicit comparison to other siblings like search_ebay.

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