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

No annotations are provided, so the description carries the full burden and does so richly: it discloses the two upstream requests, the CDN download, the language fallback ordering ('requested language, then English, then the first track; original tracks win over machine-translated'), the auto-generated caveat, the empty-caption case, and the unresolved short-link limitation.

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?

Dense and front-loaded — the core action leads, followed by provenance, fallback rules, and edge cases. Every clause earns its place, though the single long paragraph packs several distinct concerns together and could be segmented for faster scanning.

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 compensates by specifying the return shape ('plain text, timed segments (seconds) and the available languages') and the no-caption response behavior. Nothing needed to call or interpret this tool 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?

Schema coverage is 100%, so both parameters are already documented (URL-or-id format, language example). The description adds value beyond the schema by explaining the fallback selection logic for `language`, which the schema does not convey.

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: 'Video captions as text ... takes a TikTok video URL or id, reads the video's own caption tracks ... downloads one WebVTT file from TikTok's CDN.' An agent can distinguish this from the large sibling set without opening the schema.

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 clear context for when this applies and its limits: 'These are TikTok's existing captions ... nothing is transcribed', 'Many videos have no captions; the response says so clearly', and 'Short links (vm.tiktok.com) are not resolved.' However, it never names or contrasts the closest sibling (video_captions), leaving the agent to infer which of the two to pick.

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