list_product_catalogs

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

No annotations are provided, so the description carries the full burden. It only states the action and scope, but does not disclose pagination behavior (e.g., whether 'all' means all pages or just the first page), ordering, or that this is a read-only operation. The phrase 'List all' may mislead given limit/offset parameters exist.

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 sentence that is directly to the point, front-loaded with the action and resource. It contains no filler or redundant information.

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?

With no annotations and no output schema, the description is too minimal to be complete. It does not mention return value structure, pagination behavior, or clarify the potential conflict between 'list all' and the limit/offset parameters. A more detailed description is needed for an agent to invoke this tool correctly in varied contexts.

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 descriptions for publisher_id, limit, and offset (100% coverage), so the schema carries the parameter documentation. The description adds no additional semantics beyond what the schema states, such as the default limit or pagination usage.

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 'List all product catalogs for a publisher' clearly specifies the action (list), the resource (product catalogs), and the scope (for a publisher). This distinguishes it from siblings like get_product_catalog (single) and search_product_catalog_items (search/filter).

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 gives no guidance on when to use this tool versus alternatives such as search_product_catalog_items or get_product_catalog. It does not mention scenarios where one should prefer this tool or any exclusions.

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