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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is covered. The description adds only the brand-scoped nature of the search; it says nothing about pagination behavior (the cursor parameter implies paging) or result ordering, so value added beyond structured fields is modest.

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 sentence with no filler or redundancy. It is efficient, though the terseness is part of the problem rather than the solution given the undocumented parameters.

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 five-parameter, zero-coverage search tool with pagination and filtering capabilities, the description is far too thin. It does not need to explain return values (an output schema exists), but it should convey what can be searched, how results are limited order/paged, and how it relates to sibling media tools.

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?

Five parameters with 0% schema description coverage, so the description must carry the burden and it largely does not. Only 'brand' (brandId) is implied; the query string, kind enum, limit, and cursor parameters are undocumented anywhere, leaving key search semantics unexplained.

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 (media assets) and adds a scoping qualifier ('belonging to a brand'). However, it does no work to distinguish itself from near-siblings like search_library_ads, search_advertisers, or import_media, so an agent gets the 'what' but not the 'which'.

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 prerequisites, and no mention of alternatives. With several search_* and media-related siblings in the list, the description leaves the selection decision entirely to inference.

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