Search Tradera

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

Without annotations, the description discloses a key prerequisite (TRADERA_APP_ID and TRADERA_APP_KEY) and registration link, which is valuable. However, it does not describe return format, rate limits, safety, or side effects. Since it's a read-only search, some transparency is implicit, but the description could do more.

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-loaded with purpose, and includes necessary prerequisite info. Every word earns its place, and there is no fluff or redundancy.

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 description covers authentication prerequisites and identifies the resource, but it lacks guidance on parameter usage, search behavior, or integration with list_* sibling tools for category/county IDs. With an output schema present, return values are not required, but the description could still be richer for a 5-param tool.

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 0%, so the description must compensate. It provides no explanations for the 5 parameters, leaving optional filters like county_id and category_id ambiguous. The only implied param is 'query' from the tool's purpose. It does not point to sibling tools for valid ID lists, which would be helpful.

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 Tradera.com for second-hand listings/auctions, using a specific verb and resource. It distinguishes itself from sibling tools by naming the platform explicitly (e.g., search_blocket, search_vinted). The mention of 'official API' adds clarification.

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 context implies this tool is for searching Tradera, but it does not explicitly discuss when to use it vs alternatives. No exclusions or alternative tool references are provided, which would have elevated the score. The prerequisite mention is useful but not a usage guideline.

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