marketplace_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds one genuinely useful behavioral note: write queries in the native style of local sellers (Hebrew/English). However, it says nothing about pagination, result ordering defaults, rate limits, or that location defaults to telaviv. With annotations carrying the safety burden, a 3 is appropriate.

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?

Three short sentences, front-loaded purpose, then routing, then a practical query hint. Nothing is wasted.

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 9-parameter, no-output-schema tool with a 22% schema coverage, the description covers purpose and routing well but is thin on parameter guidance and behavioral details like default location and result counts. Adequate but leaving clear gaps an agent would need to infer from schema enums.

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 only 22%, so most of the 9 parameters lack schema documentation. The description only addresses query syntax (native seller style, Hebrew/English), leaving sort, location, price bounds, radius, condition, max_results, and days_since_listed undocumented by description. It adds one useful point but does not compensate for the coverage 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?

States a specific verb and resource ('Raw Marketplace search for one query') and explicitly contrasts itself with marketplace_compare, naming the condition that selects the sibling. An agent can distinguish this from marketplace_listing, marketplace_compare, or marketplace_price_history without opening a schema.

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?

Explicit when-to-use ('quick looks') and when-not-to-use with the named alternative ('for price comparison or find me the best deal use marketplace_compare instead'). This is textbook routing guidance.

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