list_campaigns

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

Discloses parameter behaviors (defaults, max, filtering) but does not mention authentication, rate limits, or explicitly state read-only nature. Annotations absent, so description carries full burden but is incomplete on safety profile.

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?

Extremely concise. Purpose stated upfront, then bullet-like arg descriptions. No wasted words, every sentence adds value.

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?

Tool has 4 params, no required params, and an output schema. Description covers main aspect (list campaigns) and parameter details. Lacks usage guidelines and safety context, but for a list tool with output schema, it is reasonably complete.

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 has 0% description coverage. Description compensates by explaining limit (max items, default, max), offset (pagination), status (filter with examples), fields (comma-separated). Adds significant meaning beyond schema.

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?

Clear verb 'List' and resource 'advertising campaigns'. Distinguishes from 'get_campaign' but no explicit differentiation from other list tools among siblings.

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 guidance on when to use this vs alternatives like 'get_campaign' or other list tools. No context on prerequisites or intended use cases.

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