get_custom_html_ad_item

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'get details' which implies a read operation, but it does not specify whether the item must exist, what permissions are required, what response structure to expect, or whether any fields are omitted. The description adds no behavioral context beyond the tool name.

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 concise sentence that states the verb, resource, and scope with no unnecessary words. It is front-loaded and straightforward.

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 has a single parameter and no output schema or annotations, so the description is the only source of behavioral info. It adequately identifies the purpose but leaves gaps: it doesn't describe what 'details' includes, how to handle not-found cases, or how it differs from the draft_get_custom_html_ad_item counterpart. For a simple getter, this is sufficient but not comprehensive.

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 fully documents the single parameter (id) with a description ('Ad item ID'), so the baseline is 3. The description adds minimal meaning by saying 'specific' and tying the ID to the custom HTML ad item, but it does not elaborate on constraints, formats, or possible values.

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 specific verb ('get') and clearly identifies the resource ('details of a specific custom HTML ad item'), distinguishing it from sibling tools like list_custom_html_ad_items (list) and get_custom_html_ad_item_conversion_tag (tag retrieval). The word 'specific' implies lookup by ID, matching the required id parameter.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this tool is for live (non-draft) items, distinguishing it from draft_get_custom_html_ad_item, nor does it advise using get_custom_html_ad_item_conversion_tag for conversion tags. An agent must infer usage solely from the tool name.

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