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

The annotations mark the tool as read-only and open-world, and the description adds useful operation-specific context: photo posts return all images in mediaUrls and each call costs 1 credit. It does not describe error behavior, rate limits, or cache behavior beyond the exposed parameter name.

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 with no filler. The purpose is front-loaded, followed by return fields, accepted inputs, and cost.

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, the description does a good job listing the returned metadata and noting photo-post media URLs. Input forms and credit cost are covered, though cache_max_age is left unexplained.

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 only 50%. The description usefully clarifies that URLs, vm.tiktok.com share links, and numeric IDs are accepted, but it completely omits cache_max_age, leaving one parameter undocumented in both the schema and description.

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 resource and verb: full public metadata for one TikTok video or photo post. The phrase 'one TikTok' and the field list clearly distinguish it from sibling list/search tools such as tiktok_userVideos or tiktok_popularVideos.

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?

Clearly implies use for retrieving a single TikTok's details rather than searching or listing, and specifies accepted input forms. It does not explicitly name alternatives or exclusions, such as using tiktok_comments for comment threads or tiktok_transcript for transcripts.

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