get_ad_video

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

No annotations provided, so description carries full burden. Discloses return values, token behavior (optional, uses cached), and edge cases (errors when account_id missing). No contradictions with annotations (none present). Could mention rate limits or data freshness, but overall good.

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?

Description is longer but well-organized: main purpose, return values, parameter guidance, and token note. Could combine the token note with parameter list, but no fluff. Front-loaded with key purpose.

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?

Despite not seeing output schema, description covers return values (URL, thumbnail, metadata). Handles parameter interactions and token behavior. For a tool with 4 params (none required) and no required auth noted, this is complete.

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 coverage 0%, description fully compensates. Explains ad_id purpose (auto-extract), video_id usage (direct from get_ad_creatives), account_id benefit (acts as relevant for token scope), and access_token optionality. Adds significant meaning beyond bare schema properties.

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?

Clear verb+resource: 'Get video details and source URL for a Meta ad video creative.' Specifically states what it returns (source URL, thumbnail, metadata). Distinguishes from siblings by referencing get_ad_creatives and differentiating from get_ad_image.

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?

Explicitly explains when to use ad_id vs video_id vs account_id, with a strong recommendation for account_id to avoid errors. References get_ad_creatives as a source for video_id. Does not explicitly state when not to use this tool, but provides enough context for proper selection.

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