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

Annotations already cover the safety profile (readOnly, non-destructive), yet the description adds substantial behavioral context the schema cannot convey: null-vs-omitted semantics, readback_omitted_fields/creative.omitted_fields, the bounded 20-campaign hint limit, and the response_budget_exceeded recovery path. It also clarifies that 'complete' means entity coverage, not field equality.

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 core read scope and batch limit are front-loaded in the first sentence, and every subsequent sentence carries non-redundant operational detail. It is a dense single paragraph rather than a structured breakdown, which makes the later caveats slightly harder to scan.

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?

With no output schema, the description takes on the burden itself and does so: it enumerates the returned field families (status, budget/bid, objective, schedule, Smart+/Spark, creative variants, attribution links). Combined with the null/omission semantics, an agent has everything needed to interpret results.

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 must carry parameter meaning, and it does for the entities array: max 50 items, entity_type scope, the campaign_id parent hint for Smart+ fields, and the adset/ad_group alias. connection_context is never explained, which is the one gap preventing a 5.

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 (read) and resource (live allowlisted TikTok configuration) with scope (up to 50 tenant-owned campaigns/ad groups/ads in one server-side request). It also explicitly distinguishes itself from the write-recovery sibling operations_get, so the agent can route without opening either 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?

Gives clear conditional guidance: use this to compare against an approved draft, and use operations_get to recover uncertain writes. It also prescribes batch behavior on response_budget_exceeded (follow next_action, do not retry or fan out). It never states when this read is the wrong choice versus metric/insight siblings, so it stops short of full when/when-not coverage.

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