List products

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

The description discloses that this is a read operation returning a single page, which implies pagination and read-only behavior. However, with no annotations, it omits details like error handling, pagination edge cases, or any side effects. It meets the minimum bar but lacks richer behavioral context.

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?

A single, focused sentence that states exactly the core function. It is front-loaded with the essential information and contains no unnecessary words.

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 a simple list tool with fully documented optional parameters, this description is largely complete. It does not describe the return format, but the tool name and title make it obvious that products are returned. The lack of an output schema is not problematic here.

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 input schema already provides full descriptions for both page and pageSize (100% coverage). The description adds no additional parameter meaning beyond what the schema states, so it earns the baseline score.

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 'Fetch a page of products' uses a specific verb and resource, making it clear what the tool does. It distinguishes the tool from siblings like list_customers or upsert_product by naming both the action and the target entity.

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?

No usage guidance is provided. There is no mention of when to choose this tool over alternatives, nor any exclusions or context about other list tools. The description only states what it does, not when to use it.

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