vestiaire_search_sellers

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

With no annotations, the description carries the full burden. It does disclose that this is 'Public data, sourced from Vestiaire Collective's own member-search service,' implying a read-only, safe operation. However, it does not describe the result shape (list vs. single object), pagination, or behavior when no matches are found. Some useful context is provided, but not comprehensive behavioral detail.

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 sentences with no wasted words. The first sentence states the core purpose, the second elaborates the search scope, and the third provides the downstream usage and data source. Every sentence earns its place and the key information is front-loaded.

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 simple single-parameter search tool, the description is nearly complete. It explains what is searched, that results contain an id, and how that id can be used downstream. The main gap is that it does not explicitly state whether the result is a list or a single object, and there is no output schema to fill that gap. Still, an agent can invoke it correctly with the information given.

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%: the single required parameter q is documented as 'Seller username or first name to search for.' The description essentially repeats this ('by username or first name') without adding new parameter-level meaning. Baseline 3 is appropriate since the schema already fully covers the parameter.

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 states a specific verb and resource: 'Search Vestiaire Collective sellers by name.' It further clarifies the search scope ('by username or first name') and distinguishes itself from the sibling vestiaire_seller by explaining that a matched result's id feeds into that endpoint. This is a precise, non-tautological purpose statement.

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 context for when to use the tool: when searching sellers by name. It also provides a downstream routing hint ('A matched result's id can be passed directly to GET /vestiaire/seller'), which tells the agent what to do after getting a result. However, it does not explicitly state when not to use it or name alternative search tools like vestiaire_search, so it stops short of full exclusion guidance.

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