list_products

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

With no annotations, the description must disclose behavioral traits itself. It only mentions pagination, which is somewhat helpful, but omits whether the operation is read-only, the default result ordering, or any constraints on the catalog search (e.g., whether it returns all products or only in-stock items).

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 a single, efficient sentence that says exactly what the tool does without redundancy. It is appropriately sized for a simple list endpoint.

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 has only two well-documented parameters and an output schema, so invocation is clear. However, the description omits any guidance on how this tool fits with siblings (e.g., using get_product for details), and the lack of annotations leaves safety/read-only status uncommunicated. Overall, it is minimally viable but with gaps.

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 descriptions cover 100% of parameters, so the baseline is 3. The description's mention of 'pagination' adds minimal extra meaning beyond the schema's limit/offset descriptions, so it does not elevate the 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 states the action ('Search') and resource ('product catalog'), and adds pagination as a key behavior. It is clear enough to distinguish from siblings like get_product (singular) and cart operations, though 'search' is slightly vague since the only parameters are pagination controls, not query terms.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that get_product is for individual product details or that cart tools are for cart operations, leaving the agent to infer the appropriate context.

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