Get product catalog

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds nothing beyond that — no note on authorization requirements, what the catalog object contains, or whether the lookup can fail for missing IDs. It does not contradict the annotations, but contributes no 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?

One short sentence with no waste, but this is under-specification rather than conciseness. Brevity here comes at the cost of any useful content.

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 retrieval tool with no output schema and a 0%-documented required parameter, the description should describe the returned catalog and the identifier's source. None of that is present, so an agent has insufficient information to invoke it correctly.

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%, so catalog_id is documented nowhere. The description does not explain what a catalog_id is, where to obtain it, or its format, which is exactly the gap it should fill for a single required identifier.

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 'Get a product catalog' merely restates the tool name and title with no additional specificity. It does not distinguish this tool from siblings like reddit_ads_list_catalogs, reddit_ads_get_product_feed, or reddit_ads_list_catalog_products, so an agent gets no signal about what makes this retrieval distinct.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent cannot tell from the text when to call get_catalog versus list_catalogs or get_product_feed, leaving routing entirely to inference from the tool name.

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