Search all sources

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

With no annotations provided, the description must carry the full behavioral burden. It discloses that results are combined and normalized, and notes Facebook Marketplace is conditional ('if enabled'). However, it does not mention side effects, rate limits, or whether it is strictly read-only, leaving some gaps for a search tool.

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?

The description is two sentences, front-loads the action, and contains no unnecessary words. Every sentence adds value: the first states what it does, the second states when to use it.

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?

The output schema exists, so return values are covered. However, the tool's complexity (aggregating multiple sources with source-specific parameters) is not fully addressed. The description mentions 'combined, normalized results' but doesn't explain how filters are applied per source, which is important for correct use.

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?

The schema has 0% description coverage, and the description does not compensate by explaining any of the six parameters. It doesn't clarify how filters like price_max or source-specific fields (blocket_category, tradera_category_id) apply across the aggregated sources. The agent is left without guidance beyond parameter names.

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 searches multiple named sources (Blocket, Tradera, Klaravik, Vinted, and optionally Facebook Marketplace) in one call and returns combined, normalized results. This distinguishes it from sibling tools that each search a single source.

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?

The description explicitly recommends using this tool for the 'weekly sourcing sweep' and mentions it as an alternative to calling each source separately. This gives clear usage context, though it does not explicitly state when NOT to use the tool.

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