get_ad_creatives

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions 'image hash resolution' as a feature, but does not explicitly state that the tool is read-only, safe, or any side effects. For a list operation, this is adequate but not thorough.

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 clear first-line summary followed by structured Args. Every sentence adds value. Slightly longer than necessary but no fluff. Front-loading of purpose is good.

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 three parameters and no output schema, the description covers what the tool does and all parameters. However, it lacks details about the return format (e.g., list of creative objects with fields) and any limitations (e.g., pagination behavior). This is a minor gap for a simple list 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?

The input schema has no property descriptions (0% coverage), but the description explains the purpose of each parameter: account_id for image hash resolution, ad_id for targeting a specific ad, and limit for pagination. This adds significant meaning beyond the 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?

The description clearly states the tool lists ad creatives for an account or specific ad, with a specific feature (image hash resolution). It distinguishes from siblings like get_creative_details (which gets details of a single creative) and create_ad_creative.

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: provide account_id to list all creatives, or ad_id to target a specific creative. However, it does not provide explicit guidance on when to prefer this over siblings (e.g., get_creative_details) or mention any prerequisites or scenarios to avoid.

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