List Catalog Items

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

There are no annotations, so the description carries the full burden. It mentions 'by CatalogId' but does not disclose pagination behavior, default page size, maximum results, error scenarios, or return format. The schema provides pageSize details, but the description itself adds little 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?

The description is a single, concise sentence that front-loads the action ('List items') and resource ('product catalog'). There is no redundancy or waste, making it easy to parse quickly.

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 simple (2 params, 1 required) with a schema that explains defaults and limits. However, the description omits return value details and pagination explicitly, and there is no output schema. It is adequate for an agent to understand the core purpose, but not fully complete for a list operation with pagination.

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% with both parameters (catalogId and pageSize) clearly described in the schema. The description only repeats 'by CatalogId' and adds no extra meaning beyond the schema. Since coverage is high, the baseline score 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 uses a clear verb-resource structure: 'List items in a product catalog by CatalogId.' It differentiates from siblings like 'list_catalogs' (which lists catalogs, not items). However, it doesn't explicitly say it returns a paginated list or mention any other filters, so it's not fully specific.

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 no guidance on when to use this tool versus alternatives. It implies you need a CatalogId (also noted in the schema), but it doesn't explicitly say 'use after list_catalogs' or contrast with other list tools. No exclusions or alternative references are given.

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