operator_resells_what

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

Annotations show readOnlyHint=true. Description adds that it's a 'sourcing feed' with ranking by score and sales, de-duped against tracked ASINs, and includes output fields. No destructive actions mentioned, consistent with annotations. Adds useful behavioral context.

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?

Description is well-structured: starts with purpose, then usage, output details, market scope, and filters. Each sentence adds value. Could be slightly shorter, but front-loaded and clear.

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?

Given 21 parameters, no output schema, and many siblings, the description covers what the tool returns and how to filter. It lacks mention of pagination or default limit, but overall provides sufficient context for an agent to use 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 coverage is 33%, but description groups and explains all filter categories (sourcing score, sales, price, fulfillment, etc.). It clarifies the meaning of 'resold_by_contains' and the shared product/fulfillment block, adding value beyond the schema.

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 finds other ASINs that operators on a given ASIN/seller resell, ranked by sourcing fit. It uses specific verbs ('find', 'surfaces') and distinguishes from siblings like operator_top_asins by focusing on 'what else does this seller carry'.

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?

Explicitly lists three use cases: 'what else does this seller carry', 'find more like this from the same operators', 'arbitrage leads from this ASIN's sellers'. Also mentions de-duping, giving clear context for when to use.

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