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

Even with readOnlyHint, openWorldHint, and destructiveHint annotations, the description adds substantial behavior: media URLs are temporary, content resolves against the US region, each successful page costs 0.2 credits, empty pages still cost, and private accounts return a forbidden error. This goes well beyond annotation defaults.

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?

The description is compact and front-loaded: the primary action is stated first, followed by pagination/ordering, then pricing, regional behavior, and error handling. Every sentence contributes non-obvious information without repetition.

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?

Given the tool's complexity and the presence of an output schema, the description covers everything needed to invoke it correctly: pagination mechanics, ordering choices, temporary media URLs, region resolution, credit costs, and private-account error behavior. No critical operational detail is missing.

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?

With 0% schema description coverage, the description carries the full burden for parameters, and it succeeds. It explains that cursor is the returned pagination value, sort_by controls latest/popular ordering, and region is fixed to the US. This adds real meaning beyond the bare schema fields.

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: 'Fetch one cursor-paginated page of current TikTok videos for a username.' It clearly scopes the tool to profile videos for a given username, distinguishing it from sibling list tools that target hashtags, music, or comments.

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?

It gives explicit operational guidance: use the returned cursor to paginate, choose latest or popular ordering, and do not retry private accounts. It does not name alternative sibling tools, but the username-based scope plus pagination/retry instructions provide clear context for when and how to use it.

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