get_campaigns_tool

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

No annotations are provided, so the description carries full burden. It only mentions retrieving campaigns with optional filtering, but does not disclose side effects (likely none), permissions, pagination, or rate limits. Minimal transparency for a data retrieval tool.

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 of 10 words, very concise. However, conciseness comes at the expense of missing crucial details. It earns a mid score because it is not verbose but could include more information without becoming long.

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?

Given no annotations, 0% schema coverage, and an existing output schema (unseen), the description is incomplete. It does not explain return format, filtering syntax, or prerequisites needed for an agent to correctly invoke the tool.

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 0% schema description coverage, the description must compensate. It mentions 'optional filtering' which hints at the filters parameter, but provides no details on format or allowed keys. The advertiser_id is partially explained via 'specific advertiser', but overall adds little value beyond parameter names.

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 retrieves campaigns for a specific advertiser with optional filtering. This verb+resource+scope pattern is specific and distinguishes it from siblings like get_ad_groups_tool (different resource) or get_gmvmax_campaigns_tool (different scope).

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?

No explicit guidance on when to use this tool versus alternatives such as get_ad_groups_tool or get_gmvmax_campaigns_tool. The description implies usage for advertiser campaigns but lacks when-not-to-use or alternative recommendations.

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