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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that the record is scoped to the domain's connected account and lists the returned metadata, but says nothing about the no-account-connected case or any error behavior — useful but not rich 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?

A single front-loaded sentence that identifies the resource and then enumerates the fields, with no filler. Nothing could be removed without losing information.

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?

There is no output schema, so naming the returned fields (id, name, currency, timezone, preview URL) is exactly the right compensation for a one-parameter read. Only the missing edge-case behavior (no ads account for the domain) keeps it from full marks.

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 100% and the single parameter is documented in the schema, so the baseline is 3. The phrase 'connected to a domain' hints that domain_id selects the owning domain, but it adds no format, lookup, or failure semantics beyond what the schema already states.

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?

Specific verb ('Get') plus precise resource ('account-level metadata for the ChatGPT Ads account connected to a domain') and an enumeration of returned fields. It is clearly distinguishable from the list-openai-ads-campaigns / ad-group siblings, though it never explicitly contrasts with the similarly named get-account-info.

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: the caller needs the ChatGPT Ads account record for a domain. No when-to-use/when-not guidance and no mention of the closest alternative (get-account-info) or of what happens if no ads account is connected to the domain.

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