Get advertisement opportunities

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the operation reads account-scoped data and OAuth integrations require the posts:read scope, which is operationally useful for auth setup.

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?

Three short sentences with no padding and the capability stated first. The only waste is the opening clause duplicating the tool title, which slightly dilutes front-loading.

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 low-complexity read-only list with two documented params, no output schema and no nested objects, the description is adequate on mechanics (auth + read scope). It does not, however, clarify what an 'advertisement opportunity' is or how it relates to the adjacent ad-network offers/reports tools, leaving sibling selection ambiguous.

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%: account resolution order and the pub_ prefixed ID pattern are fully documented in the schema. The description adds nothing about parameters, so the baseline 3 applies.

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 first sentence, "Get advertisement opportunities," is nearly a verbatim restatement of the tool title/name, so it earns little beyond the identifier itself. The resource is identifiable, but there is no differentiation from the many ad-network siblings (list_ad_network_offers, ad_network_offers_advertisements, list_ad_network_reports), which an agent must distinguish here.

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 statement of when to use this tool versus alternatives. Given four sibling tools covering ad-network offers and reports, the absence of any routing guidance is a real gap; "Reads account data" is a behavioral note, not a usage condition.

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