get_ad_details

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

No annotations provided, so the description bears responsibility. It implies a read operation and adds transparency about cached token fallback, but does not disclose potential side effects, rate limits, or authorization requirements beyond optional token.

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?

Extremely concise: two lines including header and args. No wasted words, all information is front-loaded. Every sentence 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?

With an output schema present, return values need not be explained. However, the description lacks completeness in guiding agent when to use this tool among many siblings, and 'detailed information' is vague. Minimal but functional for a simple read tool.

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 0%, so description compensates well by explaining 'ad_id' as Meta Ads ad ID and 'access_token' as optional with cached fallback. This adds meaningful context beyond the schema's type information for both parameters.

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 'Get detailed information about a specific ad' clearly states the verb and resource. It distinguishes from sibling tools like 'get_ads' (plural) and 'get_ad_creatives' by focusing on a single ad's details, though it doesn't explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives like 'get_ads' or 'get_creative_details'. The description only lists parameters without context on prerequisites or suitable scenarios.

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