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 only that the page is bounded; it says nothing about ordering, default page contents, or truncation behavior beyond what the schema's limit description provides.

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 compact sentence with no filler and the scope constraint ('one customer') front-loaded. It is perhaps too terse given the surrounding operational toolset, but nothing is wasted.

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 read-list tool in a large mutation-oriented sibling set, the description omits how results are ordered, what truncation metadata looks like (no output schema), and which alternative to use for inventory versus page listing. Annotations carry only the safety profile, so the gap is significant.

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 coverage is 67% and the schema itself documents limit and customer_id, including bounds and truncation metadata. connection_context is undocumented in both schema and description, so the description adds no parameter meaning beyond the schema baseline.

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?

States a specific verb (List) and resource (Google Ads creative assets) scoped to one customer. It is distinguishable from asset_upload/asset_link and from asset_inventory_list, though it doesn't explicitly differentiate from the closely named inventory list.

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?

No when-to-use guidance, no exclusions, and no pointer to alternatives such as google_ads_asset_inventory_list or google_ads_asset_diagnostics. The description only supplies purpose, not selection context.

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