openai ads get feed uploads

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that native fields and pagination are preserved and that processing results are included, but says nothing further about page size, defaults, or ordering; the write_schema pointer adds no behavioral clarity for a read.

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?

Only three short sentences and the purpose is front-loaded, which is good. However, the trailing write_schema sentence does not earn its place on a read-only listing tool and risks sending the agent down an irrelevant path.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations carry the safety profile; the nested query object is fully documented in the schema. The remaining gap is the misplaced write_schema cross-reference and the absence of any note on how upload statuses relate to get_feeds.

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%, so after/before/limit/paginate and the adacct_ scoping are already documented in structured fields. 'Pagination is preserved' lightly reinforces the query object but adds no syntax or limits beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List recent product feed uploads and their processing results'), which cleanly separates it from siblings like get_feeds, get_feed_products, and get_feed_settings. An agent can identify what this returns without opening the schema.

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?

No guidance on when to pick this over get_feeds or get_feed_products, nor any prerequisites or exclusions. The only pointer given ('See openai_ads_get_write_schema for nested request fields') is a write-path reference on a read-only listing tool, so it does not help selection.

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