get_ad_detail

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

With no annotations provided, this description carries the full behavioral burden, but it only reveals the verb 'Get' and the return structure. It does not mention side effects, auth requirements, error behavior, rate limits, or any other operational traits, which is a notable gap for a no-annotation tool.

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 cleanly structured with a one-line summary followed by Args and Returns sections. It efficiently uses bullet-like formatting and avoids filler, though the Args/Returns sections could be considered slightly more verbose than strictly needed.

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 2-parameter tool with no output schema, the description provides a fairly complete picture: it lists all parameters, explains their purpose, and describes the varying return shapes by ad type. It misses only the operational edge cases (errors, permission requirements), which keeps it from full completeness.

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%, and the description effectively compensates by explaining both parameters with concrete examples. It identifies advertiser_id as the advertiser's ID and creative_id as the creative/ad ID, including readable example values, making it easy for an agent to fill them correctly.

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 starts with 'Get full details for a specific ad creative,' which names a clear verb and resource. The return details (format, last_shown, content type) add specificity, but it does not explicitly differentiate from siblings like fetch_ad_creative or get_ads.

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 implied use case is clear: you need this when you have both advertiser_id and creative_id and want detailed info on a single creative. However, there is no explicit distinction from siblings or any guidance on when not to use it, leaving the agent to infer without direct routing.

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