Get ad offer advertisements

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful, non-derivable fact - the OAuth scope requirement (posts:read) - but 'Reads account data' merely restates readOnlyHint and nothing is said about pagination or response shape.

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 the core action front-loaded and zero filler. The trailing auth-scope sentence is terse and earns its place.

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 simple read-only tool with full schema coverage, complete annotations and no output schema, the description is minimally sufficient. It still leaves the agent unsure how this differs from the adjacent list endpoints, which is the main gap.

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%, so publication_id, offer_id and the optional account are all documented in the schema itself. The description adds no syntax, format, or defaulting information beyond that, 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 description states a specific verb ('Get') and a reasonably specific resource ('ad offer advertisements'), and the required publication_id/offer_id pair reinforces what is being fetched. It does not, however, distinguish itself from siblings like list_ad_network_offers or list_advertisement_opportunities, so the agent cannot tell which one to pick from the text alone.

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, no prerequisites, and no named alternative among the many ad-network siblings. The agent is left to infer that this is the per-offer detail fetch rather than a list endpoint.

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