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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful batch constraint of 1-50 ads and the scope of returned content, which the annotations do not provide. Still terse and silent on error/auth behavior for the connection_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 phrase with the verb first and no wasted words. Efficient, though extremely terse for a tool with an undocumented parameter.

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?

An output schema exists, so return values need not be described, and the annotations cover the read/safety profile. The description handles the batch-size and content scope adequately but leaves the connection_context parameter and any usage guidance unaddressed.

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?

With 0% schema description coverage, the description must carry parameter meaning. It hints at ad_ids cardinality ('1-50 ads') but never explains the connection_context token or the id format, leaving a required contextual parameter entirely undocumented.

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?

Uses a specific verb (Read) and resource (stored copy of ads), and enumerates the content returned (texts, links, button, Page, preview, type). This clearly separates it from the write-side siblings like ads_update_copy_prepare/confirm, though it never names an alternative. Clear but lacks explicit sibling differentiation.

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 phrase 'stored copy' implies this reads a cached/persisted snapshot rather than fetching live, which is an implied usage context. However, there is no explicit when-to-use, no prerequisites, and no mention of alternatives such as creatives_get or the update flow.

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