pinterest_get_catalog_inventory

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

The verb 'List' communicates a read-only operation, and 'optional product samples' hints at the includeProductSamples behavior. However, with no annotations, the description does not disclose pagination, ad-account scoping, rate limits, or return shape, sharing the full burden on the description rather than shared structured metadata.

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, front-loaded sentence with no filler. Every word contributes to the core purpose and scope.

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 tool with no annotations, no output schema, and undocumented parameters, this description is too thin. An agent cannot tell how sampleProductGroups affects results, what ad account context applies, or how this differs form catalog diagnostics/report tools.

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 the description must compensate. Only 'optional product samples' maps to includeProductSamples. adAccountId and sampleProductGroups are not semantically explained beyond their property names and default/constraint values, so an agent lacks context for those parameters.

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 and resource: 'List Pinterest catalog inventory surfaces' and enumerates the surfaces (catalogs, product groups, product group promotions, optional product samples). It clearly describes what the tool does, though it does not explicitly contrast with sibling catalog tools like diagnostics or report tools.

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 use this tool versus alternatives. The description implies a listing use case, but it gives no exclusions or routing cues relative to sibling tools such as pinterest_get_catalog_diagnostics or pinterest_run_catalog_report.

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