search_listings

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

No annotations exist, so the description carries the full burden and discloses nothing behavioral: no mention of result freshness, pagination via limit, whether results reflect live Marketplace data, or any rate/auth constraints. For a live external-scrape search tool this leaves meaningful gaps.

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 the resource and search axes front-loaded and zero filler. It is efficiently sized, though its brevity is part of why other dimensions are weak.

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?

For a 3-required-parameter search with full schema coverage the parameters are covered, but with no output schema the description could have described what a result contains and how to page through it. Minimum viable rather than complete.

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 3 applies. The description restates the query/location/filters concept but adds no syntax, default, or format detail beyond what the schema already documents for all 8 parameters.

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?

States a specific verb (Search) plus the exact resource (Facebook Marketplace listings) and the three axes of search: query, location, filters. An agent can distinguish it from get_listing (single listing) purely from the name, though the description itself never names the sibling.

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 when-to-use guidance and no alternatives referenced, despite clear siblings such as get_listing for a single item and monitor_search/monitor_search for recurring alerts. The agent must infer which sibling to pick from names alone.

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