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 without the description. Beyond that the description only adds 'with pagination', a detail already restated in the page/size schema, and says nothing about result volume, matching behaviour or what the response contains. With annotations carrying most of the load this is thin added value.

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 short sentence with the verb and resource front-loaded and no filler. It is efficient, though its brevity comes at the cost of leaving useful routing information out rather than because everything necessary was said once.

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?

A five-parameter read tool with one required array and no output schema; the schema covers parameters well, so the description needn't explain return values. However, the description leaves the agent without scope limits (how many names are sensible), result ordering expectations, or sibling routing, which is a meaningful gap for a search tool in a large toolset.

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% and the property texts are unusually rich (sort syntax, page numbering, status-to-platform-boolean mapping), so the schema does the heavy lifting. The description adds nothing about ad_names, status, or pagination semantics, which is the baseline 3 when structured fields are complete.

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 (search) and resource (ads by name) plus the source library, which is a clear statement of purpose. It does not distinguish itself from near-neighbours such as get_ad_details or search_library_creatives_by_name, so an agent cannot tell from the description alone which one to reach for.

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 description gives no when-to-use or when-not-to-use guidance and names no alternatives. The only routing hint in the whole definition (use the archived status to find an ad's id for unarchive_ad) lives in the schema property text, not the description, so the top-level text provides no usage context.

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