B2B Ad Details

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

With no annotations, the description carries the full behavioral burden and mostly fails to: it never states that this is a read-only operation, whether any auth/quota constraints apply, what happens with an invalid or expired ad URL, or how fresh the 'performance insights' are. The word 'Get' weakly implies a read, but nothing confirms it.

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?

A single front-loaded sentence with zero filler; the verb and resource come first and the enumerated contents follow. Nothing needs to be trimmed or reordered.

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?

For a tool with no annotations, no output schema, and an undocumented input, the description is too thin: it omits how ad_url is sourced, omits any routing versus search_b2b_ads, and gives no return-shape or failure behavior to compensate for the missing structured metadata.

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?

There is a single parameter (ad_url) with 0% schema description coverage, and the description never mentions it, so it does not explain what the URL should point to, how to obtain it, or whether it must come from search_b2b_ads. The schema supplies only the name and URI format, leaving the semantics of the input largely unstated.

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 states a specific verb ('Get') and resource ('detailed information about a specific B2B ad') and enumerates the payload (campaign information, creative details, performance insights). It is clear on its own, but it never distinguishes itself from the obvious sibling search_b2b_ads, so an agent gets no explicit signal on when to pick one over the other.

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 only implied: 'a specific B2B ad' hints that the tool is the detail lookup following a search, and the required ad_url suggests a prior discovery step. There is no explicit statement of when to use this versus search_b2b_ads, no prerequisites, and no exclusions.

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