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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds real value by disclosing the asynchronous/deferred nature of the operation and where the job_id originates, but omits the key behavioral question for a polling tool: what happens if the job is not yet complete, and whether results expire or must be re-fetched.

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?

Two sentences, zero waste, with the retrieval purpose and the required job_id front-loaded. Every clause earns its place.

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?

No output schema exists, so the description carries more of the burden for a retrieval tool, yet it says nothing about the return format (transcript text, status, language) or the pending-job case. Adequate for calling it, incomplete for interpreting it.

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 (job_id, timestamps) are already fully documented in the schema. The description reinforces the job_id linkage to the sibling tool but adds no syntax or semantics beyond that, so 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?

Specific verb + resource ('Get the result of a transcription') with the originating operation named explicitly (transcribe_tiktok_video). An agent can distinguish it from get_youtube_transcript and transcribe_tiktok_video without opening any 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?

States the precise triggering condition: use it when transcribe_tiktok_video started a job but did not finish in time, and pass the job_id that call returned. Clear context, though it does not contrast with get_youtube_transcript or state what to do if the job is still pending.

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