get_campaigns

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that it lists campaigns with status/budget info but does not mention pagination behavior beyond limit, nor does it confirm that the operation is read-only or any potential side effects.

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 concise with a one-line summary followed by a structured Args list. Every sentence provides necessary information without redundancy or fluff.

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?

Despite no output schema, the description covers key aspects: parameters, defaults, and filtering options. It is complete for a list tool, though return value details (e.g., fields in the response) are omitted.

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?

With schema coverage at 0%, the description adds significant value by providing an example for account_id, specifying allowed values for status_filter, and documenting default and max for limit. This compensates for the lack of schema detail.

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 clearly states the tool lists campaigns for an ad account with status and budget info. It uses a specific verb ('list') and resource ('campaigns'), and distinguishes itself from sibling tools like 'get_campaign_details' (which retrieves a single campaign) by implying a list operation.

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 provides parameter guidance but does not explicitly state when to use this tool versus alternatives like 'get_campaign_details' or 'get_bulk_insights'. It lacks exclusion criteria or usage context beyond the function itself.

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