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

With no annotations provided, the description carries the full burden. It discloses that the data is fetched 'live from Meta' and enumerates the metadata fields, which is useful. However, it does not mention any side effects (though it is clearly read-only), authentication requirements beyond the ad account ID, potential error conditions, or rate limits. For a read operation this is adequate but not richly transparent.

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 exactly two sentences with zero wasted words. The core purpose and output fields are front-loaded in the first sentence, and the usage context follows in the second. It is concise and immediately actionable.

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 metadata-fetch tool with only two required parameters and full schema coverage, the description covers the essential context: what it returns, that it's live, and when to use it. It doesn't describe the exact return structure, but since no output schema exists and the tool is straightforward, this is a minor gap. Overall, it is complete enough for an agent to call 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 100%, and the schema already provides strong semantics: catalog_id specifies it's numeric and sourced from adsap_list_catalogs, and ad_account_id explains it's required, scopes the request, and anchors the budget check. The description adds no additional parameter detail beyond the schema, so the baseline 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 states a specific verb ('Get') and a clear resource ('Meta product catalog's metadata') with explicit fields ('name, vertical, total product count, and owning business'). It also differentiates from siblings by positioning itself as a first-step overview before drilling into products, diagnostics, or data sources, which is distinct from tools like adsap_get_catalog_data_sources or adsap_get_catalog_diagnostics.

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 explicitly says 'Use as a first step before drilling into a catalog's products, diagnostics, or data sources,' giving clear guidance on when to invoke it. It doesn't mention explicit exclusions or alternatives by name, but the context makes the intended usage unambiguous. A minor gap is not stating when NOT to use it, but the guidance is sufficient.

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