depop_search_sellers

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

Since no annotations are provided, the description carries the full behavioral disclosure burden. It does add some transparency by noting the data is from Depop's public user-search API and that the result contains a username for further lookups. However, it does not mention pagination, result volume, response format/fields beyond the username, or return edge cases, leaving 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 mostly efficient and front-loaded—the core action is in the first sentence. The main flaw is slight redundancy: 'Search Depop sellers by name' and 'Finds Depop users/sellers by name or username' repeat the same core idea, so the text could be condensed into three sentences without losing value.

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 single-parameter search tool with no annotations and no output schema, the description supplies an adequate amount of operating context: what it searches, how the result can be chained into depop_shop, and the public-source provenance. It does omit the response structure details and whether multiple matches are returned, but for a simple lookup that flows into a known endpoint, it is sufficiently complete for an agent to select and call it correctly.

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 only parameter 'query' is fully described in the schema (100% coverage: 'Seller name or username to search for'). The description merely echoes that the tool finds by name or username, and the added mention of passing the matched username to depop_shop is about post-processing, not about the parameter itself. It adds no critical meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a precise verb and resource ('Search Depop sellers by name') and clarifies it finds users/sellers by name or username. It marks out a dedicated seller-lookup scope and even distinguishes itself from the shop-detail step by pointing to the next endpoint, depop_shop. This sets it apart from sibling Depop endpoints like depop_search (items) and depop_suggest.

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 gives clear contextual guidance: use it to find a seller, then pass the matched username to GET /depop/shop/{username} for the full shop. It does not explicitly name alternatives or say when not to use it, but it implies the normal flow and provides a 'next step' for the result, which is practical guidance for an agent.

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