list_products

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

The description discloses that output is derived from purchase history and is deduplicated ('distinct'), which is useful behavioral context. It lacks details such as ordering, time window, or that 'limit' controls scans rather than results, which is only covered in the schema. Without annotations, the description carries a moderate burden but is not fully transparent.

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 with no filler, front-loading the action and purpose. It is appropriately concise and every sentence earns its place.

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?

The tool is straightforward, and the description covers functionality and intended use. However, it omits return format and the meaning of 'recently,' and with no output schema or annotations, the agent gains limited context beyond basic usage.

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 single parameter 'limit' is fully described in the schema with a clear explanation ('How many recent purchases to scan'), providing 100% coverage. The tool description adds no additional parameter-specific semantics, only reinforcing the data source, so the baseline of 3 is appropriate.

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 action ('List the distinct product names sold recently') and clarifies its purpose ('discover which products exist before analyzing one'). This distinguishes it from sibling tools like get_product_sales that focus on metrics.

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 explicitly instructs when to use it ('Use this to discover which products exist before analyzing one'), giving clear context for tool selection. However, it does not explicitly name alternatives or exclusion criteria, falling just short of full guidance.

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