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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description goes further by disclosing artifact generation, a 15-minute download_url lifetime, 7-day file retention, the xdata__job__result recovery path for expired links, recovery_receipt handling for anonymous results, and the token cost per call. It is unusually rich on side effects for a read tool, though the receipt/idempotency block is dense and partly boilerplate.

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?

The purpose is correctly front-loaded in the first two sentences, but the remaining text is a long run of file-retention and receipt/idempotency policy that is hard to scan and largely reusable boilerplate. Several clauses about private recovery_receipt could be condensed without losing meaning.

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?

There is no output schema, so the description must explain returns; it does so via artifacts[] with download_url, retention windows, and the refresh path through xdata__job__result. Combined with the token-cost note, an agent has what it needs to call and recover results, with only minor gaps in pagination/filtering behavior.

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 100%, so baseline is 3; the description adds real meaning by explaining the nccAdgroupId provenance, the artifacts[] consequence of output_formats, and the full lifecycle of request_idempotency_key (reuse only to recover a lost response, new key for new execution, distinct from any provider-specific key). That is substantive beyond the schema text.

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?

Opening sentence states a specific verb and resource: 'Lists the ads (creatives) under one ad group', with the read-only scope flagged first. That is enough to separate it from naver_searchad__adgroups__read and naver_searchad__keywords__read, though those siblings are never named explicitly.

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?

It gives the prerequisite ('Connect the Naver Search Ad account first') and tells the agent where the required id comes from ('Pass the ad group id ... from the ad group list'). It does not state when a different tool would be preferable, so it stops short of full routing guidance.

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