List a seller's products

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

Annotations already indicate read-only, open-world, idempotent, non-destructive. The description adds context about pagination and sorting, and mentions the source of seller IDs. It does not contradict annotations.

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 two sentences, efficient and clear. It covers purpose and how to find seller ID without unnecessary detail.

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 the simple nature of listing with pagination/sorting, and schema covering all params, the description is sufficient. It does not detail return format, but likely not needed as it's a list with compact projection option via 'verbose'.

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 schema has 100% coverage with descriptions for each parameter. The tool description adds context about seller IDs sourcing, but parameters like sorting and verbose are already well described. No additional parameter semantics needed beyond 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 lists products for a specific seller with pagination and sorting. It distinguishes from siblings by mentioning seller context and references getting seller IDs from the 'seller' block or oskelly_get_product.

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?

It explains when to use (for a specific seller's products) and how to find seller IDs. It doesn't explicitly mention alternatives, but the sibling tools are clear enough (search_products vs seller_products).

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