get_ad

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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds useful information about review_status and typical approval timing, and the verb 'Get' implies a read operation. However, it does not disclose error behavior, response structure, or how include/ad_account_id affect the call.

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?

Two short sentences with no redundant wording. The primary action is front-loaded, and the review_status guidance is a compact, high-value addition. 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?

The tool is a simple single-resource getter, so the description covers the core invocation need. However, with no output schema and no annotations, the lack of return structure detail and undocumented optional parameters leaves some ambiguity for an agent deciding how to use include and ad_account_id.

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 description coverage is only 33%, with include and ad_account_id left undocumented. The description confirms the ad_id parameter's role but does not clarify the meaning or effect of the optional parameters. Since coverage is low, the description was expected to compensate but does not.

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 a precise verb-resource pairing: 'Get a single ad by ID.' This clearly differentiates it from list_ads and sibling getters like get_ad_group or get_campaign. The additional note about review_status confirms the tool is for retrieving one ad and monitoring its approval state.

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?

The description gives a clear use context: retrieve an ad and check review_status to monitor approval, which typically takes minutes. It implicitly tells an agent when this tool is useful after creating or updating an ad, though it does not explicitly mention alternatives or exclusions such as using list_ads when multiple ads are needed.

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