list_campaigns

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

With no annotations, the description indicates a read-only operation via 'List' and discloses the returned fields. It does not mention any other behavioral aspects such as pagination, filtering, or account scoping details beyond 'in an account'.

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 sentence with a clear structure, front-loading the verb and resource. It contains no unnecessary words.

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 with one parameter and the description covers purpose and returned fields. The presence of an output schema reduces the need to explain return values, but the description omits any mention of pagination or edge cases. It is adequate for a basic 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 only parameter, account_id, is contextualized by the phrase 'in an account', but the description does not explicitly explain the parameter or its format, leaving the schema's title to carry meaning. The description adds only minimal semantic value.

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 a specific action 'List' on a specific resource 'campaigns' within an account. The field list ('id, name, status, type, daily budget') clarifies the output scope and differentiates from sibling list tools like list_accounts or list_ad_groups.

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 usage when campaign data is needed but does not provide explicit guidance on when to choose this over sibling list tools, nor does it mention any exclusions or prerequisites. It lacks alternative references.

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