meta_join_product_insights

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'Query' and 'enrich', suggesting read-only behavior, but does not explicitly confirm safety, explain what happens when catalog access is unavailable, or describe any limitations, error cases, or rate considerations. The description only hints at a conditional join without detailing the behavior.

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 concise sentence that front-loads the core action and differentiates the tool. It wastes no words, though it could be slightly more informative without sacrificing brevity. The structure is adequate for a simple tool name and schema.

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 output schema, no annotations, and 9 parameters including a nested timeRange object, the description is too sparse to be complete. It does not mention return format, join behavior, error handling, pagination, or how parameters interact. Agents would need to inspect the schema and sibling tools to infer expected usage and output, which is a significant gap.

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 only 44%, and the description does not compensate for the undocumented parameters. It vaguely references 'product-breakdown' and 'Product Catalog metadata', which maps to productBreakdown and catalogId, but leaves metrics, level, limit, and catalogProductLimit unexplained. The description adds minimal semantic value over the schema, and with 9 parameters, more guidance is needed.

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 a specific action ('Query product-breakdown insights') and a distinct enrichment behavior ('enrich rows with Product Catalog metadata'), which separates it from sibling tools like meta_get_insights and meta_get_catalog_products. It lacks an explicit counter-reference to a sibling, so it does not fully earn a 5, but the core purpose is unambiguous.

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 phrase 'when catalog access is available' provides a conditional context for using the joining capability, implying this tool is for scenarios requiring catalog metadata. However, it does not explicitly state when to prefer alternatives like meta_get_insights (which likely omits catalog enrichment) or meta_get_catalog_products (which fetches products directly). Usage guidance is implied rather than explicit.

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