Dv360.Campaigns.List

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read, but there is no disclosure of pagination behavior, result limits, required permissions, or whether results are filtered or complete — all of which matter for a listing call with no annotation safety profile.

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 short sentence with zero filler and the scope constraint front-loaded. It is efficient, though its brevity reflects under-specification rather than precision.

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 not be explained. But for a listing tool with zero annotation coverage and no parameter documentation, the description omits pagination, filtering, and permission context that an agent would need to invoke it confidently.

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?

Only one parameter exists and schema description coverage is 0%, so the description must compensate. It does imply the parameter is the advertiser scope ('under a DV360 advertiser'), which helps an agent map advertiser_id, but adds no format, ID-source, or example detail beyond that single hint.

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 ('List') and resource ('campaigns') with the scoping entity ('under a DV360 advertiser'), which is enough to distinguish it from sibling write/update tools like dv360.line_item.update. However, it does not explicitly differentiate itself from related list siblings such as dv360.insertion_orders.list or cm360.campaigns.list, leaving the platform distinction to be inferred from the name.

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 description gives no when-to-use or when-not-to-use guidance, no prerequisites (e.g. needing an advertiser authenticated first), and no mention of alternative tools. An agent must infer usage entirely from the name and the single parameter.

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