Search TikTok locations

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

Annotations already signal readOnlyHint=true and destructiveHint=false. The description adds non-obvious behavioral context: TikTok requires both parts, so the returned `location_id` and `location_name` must be passed as `tiktokLocationId` and `tiktokLocationName` in upload_video's platformOptions. It also discloses the capability precondition. No contradiction with annotations.

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 tightly written sentences: front-loaded purpose, a precise instruction for using the result, and a capability note. Every sentence carries distinct, necessary information with no filler or redundancy.

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?

The description covers the tool's purpose, how to consume its output (via upload_video), and the availability precondition. With an output schema present and annotations covering read-only/non-destructive behavior, an agent has enough information to invoke the tool correctly. Minor omissions like result-set size or error cases are covered by structured data or are non-critical.

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?

The input schema already fully documents both parameters: `query` includes example and max length, `profile` explains it must be an Upload-Post profile name with a TikTok account connected. The description adds no additional parameter-level detail beyond referencing how the result is consumed, so it meets the baseline for 100% schema coverage.

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 verb and resource: 'Search TikTok places to tag on a post.' It clearly differentiates the tool from sibling TikTok search tools like tiktok_music_search by focusing on location/place tagging, and the purpose 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?

The description gives clear context for when to use the tool: when you need a TikTok place to tag on a post, and it explicitly conditions usage on TikTok connections that declare the `location` capability, pointing to list_users for verification. It does not explicitly contrast with alternatives, but the specialized purpose makes the condition evident.

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