get_ad_image

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

Annotations are absent, and the description only states 'Fetch a single ad image by id', which adds little beyond the tool name. It does not disclose return format, error behavior, permissions, or other operational characteristics.

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 short sentence, highly compact and front-loaded. It is free of redundancy, though its brevity leaves room for more substance.

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?

With no annotations, no output schema, and only a minimal description, the tool lacks essential context for correct selection and invocation. Sibling tools exist but are not differentiated, and parameter details are missing.

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 0%, so the description must compensate. It only implicitly covers the 'id' parameter but completely omits the 'fields' parameter, leaving half the interface unexplained.

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 verb 'Fetch' and resource 'ad image' with 'by id', clearly indicating it retrieves a single image entity. This distinguishes it from sibling tools like list_ad_images (list operation) and get_ad_creative (different resource).

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 is provided on when to use this tool versus alternatives such as list_ad_images, get_ad, or get_ad_creative. There is no mention of exclusions, use-case context, or prerequisites.

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