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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds only 'cached', hinting the choices come from a pre-fetched store (possibly stale), but says nothing about what happens on ambiguous matches or whether selection prompts further interaction.

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 the selection target front-loaded and no wasted words. Brevity is appropriate, though it edges toward under-specification rather than efficient density.

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 3-parameter tool with 0% schema description coverage, the description is too thin: it omits the meaning of two parameters and any selection-flow context. The output schema and annotations cover returns and safety, but the input side is left largely unexplained.

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 0%, so the description carries the full burden, yet it never mentions 'search' or 'ad_account_id' at all. The 'kind' values are visible only via the enum; two optional parameters remain completely undocumented in both description and schema.

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 ('Choose') and resource ('ad account, Facebook Page or Instagram account'), with the scope qualifier 'cached' and 'one' implying a single-selection picker. This implicitly distinguishes it from the many assets_list_* siblings, but never names them, so the differentiation is inferred rather than stated.

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?

There is no explicit guidance on when to use this picker versus assets_list_pages, assets_list_ad_accounts, or creatives_pick. It also never explains when to supply 'search' or 'ad_account_id', leaving the agent to guess at the selection workflow.

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