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

With destructiveHint=true already set, the description explains the mechanism behind it ('a live refresh can replace cached CTA portfolio rows for the selected advertiser') and notes server-side verification that the portfolio belongs to the same advertiser. It clarifies that complete refers to pagination, not sync coverage or permission to create, which is valuable context beyond the annotations, though it omits permission/rate-limit detail.

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?

Purpose and scope are front-loaded, followed by usage, pagination, and refresh semantics in a logical order. It is dense but nearly every sentence adds operational information; the pagination paragraph is slightly verbose but earns its length given the complexity.

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 6-parameter, paginated, refresh-capable tool with no output schema and no schema descriptions, the description covers usage, pagination, refresh behavior, and prerequisites well. It stops short of describing the returned row shape (id/name fields), which the agent must infer.

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 coverage is 0%, so the description carries the full burden and does so: it documents cursor (from previous response), limit (default 20, max 50), search (case-insensitive native id/name lookup), refresh (forces live read), and advertiser_id (required, from assets_list_ad_accounts). Only the internal connection_context is undocumented, which is acceptable.

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 and resource ('List cached TikTok CTA portfolios') scoped to 'one exact advertiser,' and names the sibling that supplies its required input ('advertiser_id from assets_list_ad_accounts'). An agent can distinguish it from the other assets_list_* tools without opening a schema.

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?

Explicitly tells when and how to use it: feed the returned id as ad_params.call_to_action_id for Smart+ website-conversion creation, never guess an id, refresh only when cache is empty or refresh=true, and keep filters/limit fixed while following next_cursor until complete=true. Names the prerequisite tool and the restart rule on a stale cursor.

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