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

With no annotations, the description carries the full burden and does reasonably well: it names the return fields (itemList, cursor, hasMore) and explains the pagination loop ('Pass returned cursor while hasMore is true'). It omits auth/rate-limit or public-visibility caveats, but for a read-only public-data tool this is solid coverage.

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?

Three sentences, front-loaded with the action, then returns, then usage/scoping. Every sentence earns its place with no repetition or padding.

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?

No output schema exists, but the description names the returned fields and the pagination contract, and clarifies content scope. It leaves the required place_id sourcing unstated in prose (relying on the schema's reference to place_detail), which is a minor gap.

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 baseline is 3, and the description adds cursor/hasMore handling semantics ('Pass returned cursor while hasMore is true') that go beyond the schema's 'pass back unchanged' note. It doesn't add detail on count/place_id, so it is a modest gain over the schema.

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 ('Get') and resource ('one native page of videos tagged to a public TikTok place'), and the scoping clause ('not a creator's current location or all content from a city') disambiguates it from sibling search/explore tools. An agent can select it without opening the 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?

'Use for location-specific content research' gives clear context, and the explicit exclusions (tagged content, not creator location, not all city content) sharpen the boundary. It stops short of naming a sibling alternative (e.g., place_detail to obtain place_id), so it lands just under full credit.

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