pinterest_get_catalog_diagnostics

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

With no annotations, the description bears the full burden and does convey that this is a read operation ('Read') and explicitly calls out that ITEMS is a read-only POST lookup. However, it omits other behavioral details such as whether some modes require special permissions, how pagination works across modes, or whether any action has side effects. It adds some transparency but not deep 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?

The description is two sentences with no wasted words. The core purpose ('Read deep catalog inventory and diagnostics') is front-loaded, followed by a compact enumeration of covered entities and a useful behavioral note about ITEMS. It is dense but appropriately sized for a broad multi-mode tool.

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?

This is a complex tool with ten parameters, nested objects, multiple modes, no output schema, and no annotations. The description lists what can be read but does not explain mode-specific parameter requirements, return value shape, pagination behavior, or how it differs from overlapping siblings. An agent would likely need external documentation to invoke it correctly with confidence.

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 20%, so the description needed to compensate for the ten parameters and mode enum. It does not explain how mode maps to the listed resources or when adAccountId, catalogId, feedId, productGroupId, or processingResultId are required. The only parameter-related hint is that ITEMS is a read-only POST lookup, which is not enough given the low 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?

The description states a specific action ('Read') and a clear resource ('deep catalog inventory and diagnostics') and enumerates the covered entities: catalogs, feeds, processing results, item issues, product groups, products, and available filters. This distinguishes it from simpler inventory tools by breadth, though it does not explicitly differentiate it from the similarly named sibling pinterest_get_catalog_inventory.

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 guidance on when to choose this tool over siblings such as pinterest_get_catalog_inventory, pinterest_run_catalog_report, or pinterest_get_organic_inventory. The description only lists capabilities and notes that ITEMS is a read-only POST lookup, but does not state conditions, prerequisites, or alternatives. An agent would have to infer usage from the mode enum.

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