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

No annotations are provided, so the description carries the full burden. It usefully discloses what it returns (native poiInfo and available place/share metadata) and a privacy boundary (does not reveal creator or viewer location), but says nothing about auth requirements, rate limits, or error behavior for a public-metadata read.

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 compact sentences, front-loaded with the core action and return shape, followed by the privacy clarification. Every sentence carries information with no 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?

With no output schema and no annotations, the description steps in to describe the return payload and scope the privacy boundary, which is enough to call the tool correctly. It is slightly thin on behavioral/operational context but adequate for a single-parameter read.

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% and the single place_id parameter is fully documented in the schema (numeric public POI ID from poi.id). The description adds the 'from video metadata' provenance but no syntax or format detail beyond the schema, so the baseline of 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 ('Get public place metadata for a TikTok POI ID') and clarifies the data source ('from video metadata'), which distinguishes it from a generic lookup. It does not explicitly name or differentiate itself from the sibling place_videos, so it falls short of a 5.

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?

The description implies when to use it ('from video metadata', keyed on a POI ID returned in a video's poi.id), but gives no explicit when-to-use, when-not-to-use, or named alternatives such as place_videos. Usage is inferable rather than stated.

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