get_ad_creatives

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

With no annotations provided, the description carries the transparency burden and does a reasonable job: it states that the tool fetches and inline-displays images, shows metadata, and explains the default full-resolution behavior plus the thumbnail option. It does not cover auth or error behavior, but for a read-oriented fetch tool the core behavior is disclosed without contradiction.

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?

Three sentences, front-loaded with the core action, no filler. Every sentence contributes either the main purpose, output content, or the one important configuration nuanance. This is appropriately sized for the tool's complexity.

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?

The schema covers all parameters and the description covers the output nature (actual images plus metadata), so the tool is callable. However, with no output schema and 7 parameters, it would benefit from mentioning what happens when no creatives exist, whether IDs must be from the same ad account, or how results are ordered/paginated. The description is adequate but not fully self-sufficient.

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 description coverage is 100%, so the baseline is 3 because the schema already documents every parameter. The description adds no essential new parameter meaning; it merely echoes the image_size default and thumbnail option already present in 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 opens with a specific verb and resource: 'Fetch ad creative images and display them inline.' It clarifies what the returned data contains (thumbnails/images plus ad metadata such as name, status, and creative ID), making the tool's purpose unmistakable and distinguishing it from sibling tools that focus on metrics or campaign lists.

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 does not state when to use this tool over siblings such as get_ads or get_creative_performance, nor does it provide when-not-to-use guidance. It implies image display is the point, but leaves alternative selection entirely to the agent.

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