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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that the page is "assembled from its server-driven UI frames," an implementation detail with little operational value, and says nothing about how merged_count/review_count/cursor paging affects the result.

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 short sentences with the retrieval purpose front-loaded and the dependency guidance second. Slightly undercut by the jargon phrase "server-driven UI frames," which consumes space without helping an agent act.

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 a full output schema, annotations, and 100% parameter coverage, the definition is minimally sufficient to call the tool. It falls short on the one thing the description uniquely must supply: disambiguating this tool from the four other tiktok_mobile_place_* siblings.

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% — every parameter including poi_id, enter_from, merged_count, review_count, and both cursors is documented in the schema. The description only repeats the poi_id provenance, adding no semantics beyond what the schema provides, so the baseline 3 applies.

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 ("Retrieve the TikTok place detail page") and grounds it in its upstream source. It does not, however, distinguish itself from the adjacent siblings tiktok_mobile_place_info, tiktok_mobile_place_photos, or tiktok_mobile_place_videos, so an agent cannot tell from the text alone which place_* tool returns what.

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 a poi_id returned by tiktok_mobile_search_place" establishes the prerequisite workflow, which is genuinely useful routing. But there is no explicit when-to-use versus place_info/place_photos/place_videos, and no note about when to page through videos or reviews versus fetching the base detail.

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