list_dv360_campaigns

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description's job is lighter. It still adds real context: a 200-item cap and the requirement that the filter be identical across pages, which is exactly the kind of behavioral constraint that isn't in the annotations or schema.

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?

Three short, front-loaded sentences with zero filler; the limit and the pagination caveat are surfaced before any elaboration. Nothing here repeats structured fields verbatim.

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 values need no explanation, and the pagination semantics are covered. But for a five-parameter tool with zero schema coverage, the undefined roles of account, page_token, and the required advertiser_id leave the agent guessing about how to scope the call 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%, so the description must carry parameter meaning, yet it only explains 'filter' (optional, native DV360 syntax, must be repeated for paging) and hints at the page_size ceiling of 200. The roles of account, page_token, and the required advertiser_id are entirely 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?

States a specific verb+resource ('List DV360 campaigns settings') and adds a scoping clarification ('These are not performance metrics') that separates it from performance-oriented siblings. It does not, however, distinguish itself from adjacent entity listings such as list_dv360_insertion_orders or list_dv360_line_items.

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?

The pagination instruction ('use the same filter when requesting the next page') is a genuine usage rule, but there is no guidance on when to call this instead of the sibling listing tools or what an appropriate advertiser_id/account context is. Usage is implied rather than advised.

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