list_products

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

With no annotations, the description carries the full burden. It discloses pagination, filtering, and that rows contain fields including vid for crosslist. It does not mention authentication or rate limits, but the tool appears read-only and safe, and the description adds useful context about the output.

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: one for purpose, one for output content. No fluff, no repetition. 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 description covers the main purpose and output fields, and hints at relationships with other tools. However, with 7 parameters and no output schema, it would benefit from explaining the paginated response structure (e.g., total count, next page) or providing an example.

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 100%, so baseline is 3. The description adds value beyond the schema by explaining the tool's purpose, the significance of the 'vid' field, and the relationship with list_channels for the source parameter.

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 action and resource: 'List the authenticated seller's FLUF products.' It also enumerates key output fields (vid, title, price, etc.) that distinguish it from sibling tools like crosslist, get_orders, list_channels, and report_bug.

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 implies the tool is used before crosslist (mentions vid used by crosslist) and references list_channels for filter values. However, it lacks explicit guidance on when not to use it or alternatives, and does not state typical use cases.

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