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 word 'compact' adds a useful hint about the payload size, but no further behavior (auth, rate limits, what fields are trimmed) is disclosed, and the output schema carries return values.

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 compact sentences with the purpose first and the prerequisite second; no filler. 'with place details' is slightly vague and partly redundant with 'place record', keeping it below a 5.

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 an output schema present, one fully documented parameter, and annotations on the safety profile, the description covers what an agent needs to call it. The only real omission is disambiguation from tiktok_mobile_place_detail.

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 poi_id is already fully documented, and the description merely repeats that it comes from tiktok_mobile_search_place. No format or example value is added beyond 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 (Retrieve) and resource (TikTok place record) and signals a 'compact' payload. It is not distinguished from the sibling tiktok_mobile_place_detail, so an agent cannot tell from the text alone how this differs from the full detail tool.

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 a clear prerequisite: the poi_id must come from tiktok_mobile_search_place, which is real routing guidance. It offers no exclusions or comparison against tiktok_mobile_place_detail, place_photos, or place_videos, so the when-not is left implicit.

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