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

Beyond the readOnly/openWorld annotations, it discloses non-obvious traits: the data comes from a rendering residential proxy, the view is logged out and therefore truncated to the first 4 cards, pricing is $0.02 USDC per successful call via x402 on Base/Solana/Arc, and failed calls are not charged. These are exactly the facts an agent needs before spending money.

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?

Two sentences, front-loaded with the resource and returned fields, then the source/payment mechanics. Dense and slightly run-on in the field list, but every clause (proxy, 4-card limit, price, no charge on failure) carries information an agent would otherwise have to discover.

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 an output schema exists, the description needn't explain return values in depth, and it still enumerates the key fields. Combined with coverage limits and billing terms, an agent has enough to call it correctly; only explicit alternative-tool routing is missing.

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 100%, so the enum values (7/30/180 days) and two-letter country codes are already documented. The description only restates that results are scoped by region and period, adding no format or default information beyond the schema. Baseline 3 is appropriate.

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?

The description states a specific resource: top-performing TikTok auction ads from the Creative Center public gallery, with the exact fields returned. It is clearly distinct from the sibling TikTok tools (profile, hashtag analytics, comments), although it never names a sibling to contrast with. No explicit verb, but 'the top-performing ads the public gallery shows first' is unambiguous.

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?

Usage is implied by 'for a region and period' and by the note that this is the logged-out view showing only the first 4 cards, which helps an agent gauge fitness. However, there is no explicit statement of when to prefer this over the other TikTok tools, nor of exclusions or prerequisites.

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