get_ad

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

With no annotations, description says it returns creative, issues, and preview link, which helps set expectations. However, it omits details like error handling, auth needs, or rate limits.

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?

Single sentence with front-loaded action and key results. Every word earns its place.

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?

Template-level tool with no output schema; description gives high-level return info but lacks details on parameter format, error cases, and edge behavior.

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 has 0% description coverage; description only explains ad_id implicitly but completely ignores the 'fields' parameter, leaving its purpose and format 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?

Clearly states verb 'Get' and resource 'single ad by ID', distinguishing it from list_ads and other get tools. Also specifies return contents: creative, issues, preview link.

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?

Implies usage when an ad ID is known, but provides no explicit guidance on when not to use it or alternatives like list_ads or get_creative.

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