getAdDetails

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

No annotations are present, so the description carries the burden of behavioral context. 'Get' strongly implies a read-only operation and the listed fields signal the returned data, but the description does not explicitly state that the tool makes no changes or explain how 'issues' are represented.

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?

The description is a single, front-loaded sentence with no filler: the verb, resource, and key output fields are all present. Every word contributes.

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 one required parameter and no output schema, the description is mostly sufficient for invoking the tool, and it names three key return components. However, 'full ad details' and 'issues' remain vague, and the lack of any output schema or behavioral notes leaves some ambiguity about the exact response shape.

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?

The schema already covers the only parameter (adId with 'Ad ID'), so the baseline is 3. The description does not add format details, examples, or constraints for adId, but it does connect the parameter to the detailed results returned.

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 the operation ('Get') and resource ('full ad details') and names specific returned fields (effective status, creative ID, issues). It does not explicitly differentiate from siblings like getAds or getAdCreatives, but the singular adId and 'full details' wording make the intended use reasonably clear.

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?

Usage is implied: call this when you have an adId and need detailed information about a specific ad. However, it does not state when not to use it or mention alternatives such as getAds for listing ads or getAdCreatives for creative content.

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