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

With no annotations, the description carries the transparency burden. It does disclose meaningful traits: the 2-credit cost, that empty/failed results are not charged, and the 24h cache behavior. However, it also states 'default always fresh', which conflicts with the schema's cache default of true, muddying the behavioral picture.

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 brief, but brevity isn't conciseness when the core action is omitted. It leads with billing ('Costs 2 credits') instead of stating the tool's function, and the two sentences don't form a clear, front-loaded definition.

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?

For a tool with no output schema and no annotations, the description must at minimum state what it returns and when to use it. It provides cost and cache behavior but never explicitly says it retrieves a TikTok transcript, and it leaves the cache default ambiguous, so the definition is incomplete.

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 a baseline of 3 applies, and the description adds little beyond the schema's already-detailed cache and language parameters. Worse, the description's 'default always fresh' contradicts the schema's 'Default true' for cache, actively reducing semantic clarity rather than adding value.

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 uses the noun 'Transcript' and never states the action (e.g., 'Fetches the transcript of a TikTok video'). The name and URL parameter hint at the purpose, but the description itself is vague about what the tool does, only providing cost and cache details.

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 no guidance on when to use this tool or how it differs from the many transcript sibling tools (youtube_transcript, instagram_transcript, etc.). The only platform constraint appears in the schema's URL parameter description, not in the tool description, so the description itself offers no usage direction.

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