meta_ads_ads_get

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

With no annotations, the description states 'Read-only' and lists returned fields. It discloses that ad_review_feedback is conditionally populated when the ad is in WITH_ISSUES. This adds behavioral context beyond just saying 'gets ad details'. However, it does not mention auth requirements or rate limits, which are minor for a read operation.

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?

Four sentences with no wasted words. First sentence states purpose, second lists fields, third declares read-only, fourth gives usage trigger. Information is front-loaded and efficiently structured.

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 covers purpose, usage trigger, field list, and read-only nature. Since there is no output schema, the return value enumeration is helpful. It lacks error handling context, but for a simple read operation this is sufficient. Slightly more detail on when not to use (e.g., use list for summaries) would improve 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 coverage is 100% with both parameters having descriptions. The tool description does not add extra meaning beyond the schema, as account_id and ad_id are well-defined in the schema. Baseline 3 is appropriate since description adds no new parameter semantics.

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 clearly states it 'fetches the full detail record for a single ad' and specifies fields like creative_id and ad_review_feedback. It distinguishes from siblings like meta_ads_ads_list by implying list returns summary data, while this tool returns full details with issues info.

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 says 'Call this when an ad shows up as WITH_ISSUES in ads.list — ad_review_feedback explains the policy rejection.' This provides a precise scenario and context for when to use the tool, guiding the agent effectively.

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