List advertisers

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

Annotations already declare read-only and non-destructive behavior. The description adds meaningful context: the pagination envelope, apiPointBalance, exact advertiser fields, and filter semantics, which go beyond annotation hints and help predict the response.

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 description is a single dense paragraph that front-loads the core action and then lays out response fields, filtering, and limits in logical order. Every sentence carries useful information, though the field enumeration makes it longer than strictly necessary.

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?

With no output schema, the description fully explains the return envelope, the extra apiPointBalance, and every item field. It also covers filtering, pagination defaults, and the absence of free-text search, making it self-sufficient for this list operation.

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 schema has 100% parameter coverage, but the description adds an important caveat: no free-text search, so names must be matched on the client side. It also reinforces filter keys and pagination defaults, adding value beyond the structured schema.

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?

The description explicitly states 'Returns one page of advertisers registered under the account', which is a specific verb+resource. It also lists the response envelope and item fields, making the purpose unmistakable and distinct from sibling list tools for other entities.

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?

It provides clear guidance on pagination, filters, and explicitly warns that free-text search is unavailable, requiring client-side name matching. While it doesn't name alternative tools, the resource and context are clear enough to avoid confusion.

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