get_ad_details

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

No annotations are provided, so the description carries full behavioral burden, and it discloses almost nothing. It does not state what happens if the ad_id is invalid, whether permissions are required, or what "details" encompasses. The existence of an output schema softens the return-value gap, but the description adds negligible behavioral context.

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?

It is a single short sentence with no waste and the resource is front-loaded, which is structurally sound. But it is terse to the point of under-specification rather than genuinely efficient.

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 output schema is present, so return values need not be explained, keeping this a simple single-resource read. Still, with no annotations and 0% parameter coverage, the definition leaves the agent guessing about the identifier's semantics and the tool's boundary with the sibling ad getters.

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 0% and the single parameter ad_id is only documented by its name and type. The description says nothing about the identifier's format, source, or constraints, so it fails to compensate for the coverage gap.

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?

States a verb (get) and resource (ad) with singular scope, which distinguishes it from get_ads by cardinality. However, "with details" is vague filler that doesn't clarify what fields are returned or how it differs from get_ad_creatives/get_ad_previews.

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 versus get_ads (list) or the other ad-related getters. Usage must be inferred entirely from the tool name and the fact that ad_id is required.

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