openai ads get feed settings

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 in the response, which is modest but genuine context about output shape. It does not mention any auth/account scoping or failure behavior, though the schema does.

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 purpose sentence is front-loaded and efficient. However, the trailing sentence directing the agent to openai_ads_get_write_schema for request fields does not earn its place in a read-only tool with no request body, and reads as boilerplate noise.

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 and annotations are rich, so return values and safety need not be spelled out. What is still missing is any indication of how the returned settings relate to the sibling feed endpoints, leaving the agent to infer placement from the name alone.

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% and both parameters are documented in detail, including the adacct_ pattern and account-scoping rule. The description contributes no additional parameter meaning, so the baseline of 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: read a feed's display and organic-listing settings. The resource scope is narrow enough to distinguish it implicitly from siblings like openai_ads_get_feed_products and openai_ads_get_feed_uploads, but no sibling is named outright.

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 statement of when to call this versus openai_ads_get_feeds or any other feed-related sibling. The only routing sentence points at openai_ads_get_write_schema for 'nested request fields', which is confusing for a read-only tool and gives no selection guidance.

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