Get one ad account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the REST path (GET /v1/ad-accounts/{id}), which restates the read nature rather than adding context such as auth requirements, error behavior for unknown ids, or whether the response includes synced metrics.

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?

One sentence, front-loaded with the action, with the endpoint in parentheses as secondary detail. Nothing is wasted, though the brevity borders on under-specification rather than tightness.

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 single-parameter read tool this is close to minimally adequate: an agent knows to pass an id and expects one account back. With no output schema and no schema descriptions, the agent still lacks the id format and any notion of what the returned object contains, which the description could have supplied in one clause.

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 property 'id' is a bare string with no documentation. The description only shows '{id}' embedded in the endpoint path, hinting that it is a path parameter, but says nothing about format (numeric vs. platform-prefixed) or where the agent obtains a valid id.

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 names a specific verb and resource ('Get one ad account'), and the singular 'one' implicitly separates it from sibling adAccounts_list, which returns many. It stops short of naming adAccounts_list or adAccounts_manage explicitly, so the differentiation is inferable rather than stated.

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?

There is no when-to-use guidance beyond the implicit need to already hold an account id. Nothing tells the agent when to prefer adAccounts_list (discovery), adAccounts_manage (mutation), or adAccounts_sync (refresh), all of which appear in the sibling list.

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