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 clearly discloses that the tool serves from the workspace cache (no Meta API call) and that refresh:true forces a live re-sync, which is critical behavioral context beyond the schema. This effectively communicates the operation's side effects and performance characteristics.

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?

Two sentences with zero redundancy. The first sentence states the action and use case; the second explains cache behavior and refresh. Information is front-loaded and every word earns its place.

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 list tool without an output schema, the description covers purpose, use case, and cache/refresh behavior. It does not describe the return format or error handling, but those are inferable for a list operation. The description is complete enough for an agent to call it correctly in the intended scenario.

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%, so both parameters (ad_account_id and refresh) are fully documented in the schema. The description reinforces the refresh semantics and ad_account_id scoping but does not add new information beyond what the schema already provides. Baseline 3 is appropriate given full schema coverage.

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?

States a specific verb+resource: lists Meta product catalogs and their product sets for an ad account. Clearly distinguishes from sibling list tools (e.g., adsap_list_ad_accounts) and catalog-specific tools (adsap_get_catalog_details) by its explicit purpose. The use case for building catalog, DPA, or collection ads adds specificity.

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?

Provides a clear context for when to use the tool ('use to pick a catalog + product set when building catalog, DPA, or collection ads') and explains the cache/refresh behavior. It does not explicitly name alternative tools or state when not to use it, but the use case is unambiguous enough for an agent to select it appropriately.

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