search_sellers

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that verified=True restricts results to verified providers, but says nothing about read-only behavior, pagination, default result limits, ordering, or what the response contains.

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 definition is two short sentences and front-loads the core purpose before the verified-filter detail. It is appropriately sized, though the second sentence is slightly fragmentary rather than fully structured.

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 four-parameter search tool with no annotations and no output schema, the description is too thin. It omits pagination or limit behavior, result ordering, return shape, and how the search behaves when both q and category are supplied.

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 for all four parameters. It clarifies that q means keywords, category filters by category, and verified=True means verified providers only, but it does not explain the limit parameter, its default of 20, or how q and category interact.

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 data sellers by keywords and/or category, plus a verified-only filter. It is clear what the tool does, but it does not distinguish itself from siblings such as search_datapoints or list_categories.

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 phrase 'by keywords and/or category' implies how the search inputs can be combined, and the verified filter implies a refinement use case. However, there is no explicit guidance on when to use this versus get_seller, list_categories, or search_datapoints.

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