List catalog item issues

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only the scoping fact that results come from one processing run; it says nothing about pagination, result caps, or filtering behavior beyond that.

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?

A single twelve-word sentence with no filler, and the resource is front-loaded. It is arguably too terse rather than too long, but nothing in it is redundant.

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?

The output schema exists, so return values need no explanation, but with four undocumented parameters, no guidance on obtaining the required processing_result_id, and no note on result limits, the definition is under-specified for a tool an agent will struggle to chain 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% across four parameters, so the schema supplies only names and types. The description implies the role of processing_result_id but does not explain item_validation_issue (apparently an issue-type filter), max_results, or ad_account_id, leaving half the surface undocumented in both places.

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 names a specific resource ('item-level errors and warnings') and scopes it to a single feed processing run, which separates it from the sibling that lists the runs themselves. It is clear what the tool returns, though it omits an explicit verb like 'list/retrieve' and relies on the title and name to supply it.

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 statement of prerequisites, and no pointer to the sibling pinterest_ads_list_feed_processing_results where a processing_result_id would come from. An agent must infer the entire workflow from the required parameter name alone.

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