List products

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

With no annotations provided, the description carries the burden. It discloses key behavioral traits: 'Read-only; does not consume credits' and 'paginated'. This goes beyond simple listing by indicating safety and cost implications, though it does not detail response format or rate limits.

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 concise sentences with front-loaded action: the primary function 'List' comes first, followed by pagination, read-only, no credits, and a use case. No wasted words; every clause 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 a simple list operation with 3 optional params and no output schema. The description adequately covers purpose, usage scenario, and safety. It lacks detail on return fields, but that is not explicitly required given the straightforward nature of listing products and the absence of an output schema.

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% for all three parameters (page, status, page_size). The description adds minimal extra meaning, only mentioning pagination which is already covered by the schema. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 verb and resource: 'List the project's products' with pagination clearly indicated. It distinguishes from sibling tools like get_product (single product) and other list_* tools by explicitly mentioning 'products' and 'paginated'.

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 provides clear when-to-use guidance: 'Use before scaffolding a storefront so you generate cards for real items.' It implies this is a safe, non-consuming operation, though it does not explicitly mention alternatives or exclusions beyond the implied contrast with other tools.

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