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

With no annotations, the description must carry the behavioral disclosure burden. It does add useful context about including escrow and delivery statuses, but it doesn't disclose pagination behavior, default ordering, or whether all campaigns are returned or just active ones. For a read-only list operation, this is a moderate gap.

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, front-loaded sentence with no wasted words. The verb 'List' appears first, and the sentence concisely covers the resource and key details. The odd '[Buy]' prefix is minor noise but doesn't reduce readability.

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?

This is a simple list tool with optional parameters and no annotations or output schema. The description explains the basic purpose but omits important context such as response format, pagination, and defaults. Given the lack of other structured metadata, it should have revealed more about what the tool returns and how it behaves.

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 0% description coverage, so the description must compensate for both parameters. The phrase 'as advertiser and/or publisher' clarifies the role parameter, but limit is completely ignored. This partial compensation is insufficient for full clarity, so a score of 3 is appropriate.

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 uses the specific verb 'List' with a clear resource, 'ad campaign bookings,' and further specifies the scope by role (advertiser/publisher) and included statuses (escrow + delivery). This clearly distinguishes it from sibling tools like get_campaign (singular) and create_campaign.

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 implies when to use it: when you need to list campaign bookings for your roles. It explicitly mentions the role filtering capability, providing clear context. However, it doesn't mention alternatives or exclusions, such as when to use get_campaign instead, so it doesn't fully reach a 5.

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