firstdibs_search

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

With no annotations provided, the description carries the full behavioral disclosure burden, but it only says 'Searches or browses...' without describing result format, pagination defaults, filter combination semantics, or any constraints. An agent gets little sense of what will happen at runtime beyond the obvious search behavior.

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?

Two compact sentences with the core action front-loaded in the first sentence. The filter enumeration is long but comprehensive and not padded with filler; it earns its place given the tool's 20 parameters.

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?

This is a complex tool with 20 optional parameters, no annotations, and no output schema, yet the description provides only a general filter list. It omits guidance on how to source valid slugs, how filters interact, what the default response looks like, and any behavioral caveats—leaving a substantial gap for an agent deciding how to invoke 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?

Schema description coverage is 100%, so the baseline is 3 even without additional parameter detail in the description. The description adds only a high-level filter list, and it even introduces vague terms like 'sale' and 'seller' that do not map cleanly to schema parameters (on_sale, top_seller, recognized_seller), which slightly reduces its helpfulness.

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 opens with a specific verb and resource ('Search 1stDibs listings') and narrows the scope to handbags and purses, which clearly distinguishes it from firstdibs_categories, firstdibs_designers, and firstdibs_product. The listed filters further clarify exactly what dimensions the search supports.

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 conveys that this tool is for searching or browsing 1stDibs listings with filters, so the general usage context is clear. However, it does not mention alternatives or exclusions—for example, that category/designer slugs should be obtained from firstdibs_categories/firstdibs_designers or that product details come from firstdibs_product.

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