fo_list_catalogs

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

No annotations are provided, so the description bears full burden. It states 'list all product catalogs you have access to' but does not disclose pagination behavior, data freshness, or rate limits. The parameters 'page' and 'pageSize' hint at pagination but are not explained.

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 two sentences long, contains no filler, and each sentence adds essential information: what the tool does and why it is useful.

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 listing tool, the core purpose and return value are covered. However, missing details about pagination handling and output structure (since no output schema) leave gaps for an agent.

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 0% and the description does not mention the two parameters (page, pageSize) at all. With no parameter explanations, the description adds no value beyond the schema field names.

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 clearly states the tool lists all accessible product catalogs and explains the return value (catalog IDs) and its purpose for subsequent product searches. This distinguishes it from sibling tools like fo_search_products and fo_list_advertisers.

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 implies that the tool should be used before product searches to obtain catalog IDs, providing clear context. However, it does not explicitly mention when not to use it or compare it to alternatives like fo_search_products_full.

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