Dv360.Advertisers.List

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about read-only semantics, required DV360 permissions/scopes, pagination, or result limits. Since an output schema exists, return-shape explanation is not required, but the operational traits are absent.

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?

One short, front-loaded sentence with no filler. Its brevity is appropriate in form, though it edges toward under-specification rather than true conciseness.

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 tool is simple (one required param, output schema present), so the bar is low, but the only input remains undefined and there is no mention of pagination or result size. Adequate to identify the call, not adequate 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?

The single parameter partner_id has 0% schema description coverage, and the description offers no clarification of what a partner ID is, its format, or how to obtain it. With the schema contributing nothing, the description should compensate but does not.

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?

Clear specific verb ('List') plus resource ('advertisers') and a stated parent scope ('under a DV360 partner'). It does not distinguish itself from adjacent DV360 listing siblings such as dv360.campaigns.list or dv360.insertion_orders.list, so an agent gets the action but not the full positioning.

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 explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g. that a partner must exist first, or when to pick this over campaigns/insertion order listings). Usage is only inferable from the tool name and the phrase 'under a DV360 partner'.

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