get_google_ad_details

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

The description expands beyond the readOnlyHint annotation by detailing the returned data (text variations, image URLs, headlines, descriptions). This adds valuable context about the tool's scope and output, though it doesn't address edge cases or response structure.

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 well-structured sentences front-load the purpose, then provide usage guidance and rationale. Each sentence adds value with no redundancy or filler, making it concise and easy to parse.

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 a single parameter, read-only annotations, and no output schema, the description adequately covers what the tool does, where the input comes from, and expected data content. It also mentions practical use cases like media extraction and visual analysis, leaving little ambiguity for typical usage.

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?

With ad_url having no schema description (0% coverage), the description compensates by specifying the parameter's source ('adUrl from get_google_ads') and its role in identifying a specific ad. This provides meaningful semantic context, though exact formatting or validation rules are not mentioned.

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 the specific verb 'Get' and resource 'detailed information about a specific Google ad,' listing concrete data types like variations, regional stats, and impressions. This clearly distinguishes it from siblings like get_google_ads (which lists ads) and analyze_ad_image (which analyzes images).

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?

It explicitly instructs to use this tool with the adUrl from get_google_ads, providing a clear integration path and use case ('analyzing ad content and extracting media URLs'). While it doesn't explicitly state when not to use alternatives, the context is clear and actionable.

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