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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. However, the description adds no behavioral details beyond that—it does not mention that transcripts may be unavailable, that network access is required, or that language and AI fallback options exist (which are only in the schema).

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 a single, concise sentence that efficiently communicates the core purpose. It adds the word 'spoken' and the 'by URL' qualifier, giving slightly more specificity than the title, with no wasted words.

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 simple getter tool with three parameters and no output schema, the description is minimally adequate. However, it lacks context about return format (e.g., text vs. structured JSON), potential failure modes, and the optional parameters' behavior, which could leave an agent uncertain about what to expect.

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 description coverage is 100%, so all three parameters are already documented with clear descriptions (URL, language, and useAiFallback). The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 ('Get') and resource ('spoken transcript') and specifies the platform ('TikTok') and input method ('by URL'). While it is clear, it largely restates the title and does not distinguish itself from the many sibling transcript tools beyond the platform name.

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 provides no guidance on when to use this tool versus alternatives (e.g., facebook_post_transcript_get or youtube_video_transcript_get). It does not mention when not to use it, prerequisites (like public video), or alternative routes for transcripts on other platforms.

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