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

Adds substantial context beyond readOnlyHint/openWorldHint: automatic language detection, a 20-60 second latency expectation, per-day and per-video-length free-use limits, and the async job_id behavior when the call returns early. These are exactly the operational facts annotations do not convey.

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 tight sentences: purpose first, then latency, then limits and async follow-up. Every sentence carries distinct operational information with no filler.

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 carries the return-value burden and does explain the partial/failure case (job_id). It stops short of describing the shape of a successful result (plain transcript text, timestamps prefixing when enabled), which is the only notable gap.

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 the url and timestamps parameters (including the [0:12] format example and default) are fully documented in the schema. The description adds only 'from its link', which restates rather than extends the schema, so the baseline 3 applies.

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 (transcribe speech in a TikTok video) and the input source (its link). The TikTok scope implicitly separates it from get_youtube_transcript, and it names get_transcription_result as the async follow-up.

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 routing guidance: if the call returns before completion it hands back a job_id for get_transcription_result, so the agent knows the async alternative and the condition that selects it. It does not explicitly state when to prefer get_youtube_transcript over this tool, but that is inferable from the resource.

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