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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the word 'cached', which hints the selection comes from previously listed assets, but does not explain cache staleness, whether the pick is persisted, or how it relates to the connection_context parameter.

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 nine-word sentence, front-loaded with the verb and the three options. No waste, but underspecified rather than tight.

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?

An output schema exists so return values need no explanation, but with 0% parameter coverage, no usage routing against ~90 siblings, and only 'cached' to convey behavior, the description is too thin for a tool that gates access to the three core asset types.

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 parameter burden, yet it only implies that 'kind' selects among the three asset types and says nothing about 'search', 'ad_account_id', or 'connection_context'. For a 4-param tool with an opaque mctx_v1_ pattern, this is a real gap.

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?

Specific verb 'Choose' with three concrete resource types (ad account, Page, Instagram account). Clear what it does, but 'cached' is the only qualifier and it doesn't distinguish itself from siblings like accounts_list_eligible_pages or assets_list_pages, which also surface similar entities.

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 mention of alternatives, no criteria for selecting one of the three kinds. The agent must infer that this is a picker for an existing cache versus the search/list siblings, and nothing in the description says so.

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