get_ad_creative

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

No annotations are provided, so the description carries the full burden. 'Fetch' implies a read-only operation, but the description does not disclose details about return format, pagination, errors, or any potential side effects. It provides basic transparency but lacks depth beyond the action itself.

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 sentence, front-loaded with the verb and resource, and contains no filler. It is appropriately concise for a simple get-by-id tool.

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 description is minimal and covers the core purpose but lacks information about optional parameters, return value, or constraints. Given the presence of a sibling 'list_ad_creatives' and an undocumented 'fields' parameter, more context would be beneficial. Still, for a straightforward get, it is almost viable.

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 0%, so the description must compensate. It adds meaning for 'id' by indicating lookup by identifier, but completely fails to explain the 'fields' parameter. The schema only provides type/pattern, leaving the semantics of fields undocumented.

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 identifies the resource 'ad creative' with the scope 'single... by id' clearly. This distinguishes it from sibling tools like list_ad_creatives and get_ad.

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 for retrieving a specific ad creative by ID, but does not explicitly state when to use this vs. list_ad_creatives or mention any alternatives. The context is somewhat clear from the wording but lacks explicit guidance.

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