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

No annotations are provided, so the description carries full behavioral burden. It does disclose the return grouping ('seller × condition × price'), which is genuine added context, but never confirms this is a read-only operation, says nothing about pagination behavior despite page/size parameters, and gives no hint about result volume or ordering.

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 sentences, zero waste; the capability statement is front-loaded and the prerequisite follows. Nothing repeats the schema or restates the tool name.

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 an 8-parameter tool with no annotations and no output schema, the description covers purpose and the product_id prerequisite but leaves the agent guessing about pagination, result size, and the unexpected notification_message parameter on what appears to be a search operation. Adequate to invoke, incomplete to invoke well.

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 63%, so several parameters (page, size, ships_from, notification_message, min/max price) rely on the schema alone. The description does implicitly signal the seller/condition/price filter dimensions, but adds no unit, format, or default guidance beyond what the schema already says.

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?

States a specific verb and resource ('Find individual seller listings for a specific product') plus the result shape ('grouped by seller × condition × price'), which separates it from get_pricing's aggregate view. It also positions the tool relative to search_cards, so an agent can place it in the workflow without opening another schema.

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 prerequisite is explicit and actionable: 'Use search_cards first to get a product_id', which matches the single required parameter. It stops short of stating when-not to use it (e.g. when aggregate pricing is enough, use get_pricing), so it is clear context without exclusions.

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