list_creatives

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

Description lists returned fields, which is helpful, but does not disclose pagination behavior, rate limits, authentication requirements, or that it is a read operation. With no annotations, the description carries the full burden and only partially addresses it.

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?

Two concise sentences: first defines purpose, second lists return fields. No fluff, front-loaded information.

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?

For a tool with 4 parameters and no output schema, the description only covers purpose and return fields. Missing explanations for pagination parameters and how to specify fields. Adequate but not thorough.

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 coverage is low (25%), and the description adds no meaning to parameters beyond the schema. It does not explain 'limit', 'after', or 'fields', leaving the agent to infer their usage.

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 action (list), the resource (ad creatives), and the scope (in an account). It distinguishes from sibling tools like 'get_creative' (single creative) and 'create_ad_creative' (creates).

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 tool versus alternatives such as 'get_creative' or other list tools. No context about prerequisites or filtering options.

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