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

No annotations provided, so the description carries full burden. It thoroughly discloses behavior: pagination mechanics (cursor, limit, search, complete flag semantics), the meaning of 'complete' (pagination only, not sync coverage or permissions), handling of rejected/old cursors, the advertiser_id filtering behavior, and the prepare step verification. This goes well beyond minimal disclosure.

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 description is detailed but every sentence earns its place: purpose, data shape, pagination rules, creation flow, and an example. It is front-loaded with the core function, then logically proceeds through details. No redundancy or filler.

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?

Given there is no output schema, the description covers return shape (linked_bcs), pagination, error recovery, and the creation-related filtering. It also warns about misinterpretation of 'complete'. It provides everything an agent needs to call the tool correctly and interpret results, including a usage example.

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 has 0% description coverage, so the description fully compensates. It explains limit (default 20, max 50), search (case-insensitive native id/name lookup), cursor (from previous response), and advertiser_id (from assets_list_ad_accounts for exact cached advertiser link). Each parameter's purpose and constraints are defined.

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 (List), resource (cached TikTok pixels), and context (authenticated tenant, owning BC list attached). It clearly distinguishes this from sibling asset listing tools by focusing on pixels and cached data, and the mention of linked_bcs adds unique scope. No ambiguity.

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?

Provides clear context for when to use the tool: it is the pixel-specific listing tool, and it explicitly mentions the creation flow with advertiser_id from assets_list_ad_accounts, giving a conditional usage. It also gives pagination guidance (keep same tool/filter/limit). However, it does not explicitly state when NOT to use it vs other asset types, though the name and focus make that implicit.

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