List Ads Campaigns

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

With no annotations, the description carries the behavioral burden and does disclose important prerequisites: OAuth2 is required and Mercado Ads must be enabled for the account. It also clarifies the data is limited to the authenticated seller's campaigns. It doesn't discuss pagination/limits or empty-result behavior, but the output schema covers return shape.

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 compact and front-loaded: purpose, prerequisites, then concrete examples. Every line contributes to correct selection/invocation, and the examples are scannable.

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 prerequisites, country/site context, and natural-language examples make the tool callable for common cases, and an output schema exists so return values don't need to be restated. The main gap is that account and limit are not covered in the description, but the examples cover the most frequent invocation patterns.

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 compensate, but it only demonstrates site_id and status through examples. There is no explanation of limit or account in the description, so an agent relying solely on this description would not fully understand those parameters.

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 opens with a clear verb and resource: 'List Mercado Ads campaigns for the authenticated seller in a given country.' This distinguishes it from sibling item/order/search tools by naming 'Mercado Ads campaigns' and country scoping. It doesn't explicitly name a sibling alternative, so it stops short of a 5.

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 usage examples imply when to use the tool ('Show my active advertising campaigns', 'List my Mercado Ads campaigns in Uruguay') and map to site_id/status. There is no explicit guidance on when not to use it or which sibling to prefer, so usage guidance is contextual but not fully explicit.

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