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

Annotations already indicate read-only, open-world, and non-destructive behavior. The description adds valuable context beyond that: transcripts are canonical and reused, content does not expire, and the request is metered and may take longer when generation is needed. This gives the agent useful expectations about latency and resource usage, which annotations do not cover.

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 two sentences long and front-loaded with the core purpose. Every sentence adds useful information: the first defines the action and scope, the second covers output format, caching, and performance characteristics. There is no redundant or vague wording.

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?

Given the tool's simplicity (one parameter, output schema exists, annotations present), the description covers all essential aspects: what it returns, caching semantics, and metering/latency caveats. It does not need to detail return values since an output schema exists, and it provides enough operational context for an agent to use it correctly.

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?

The input schema has a single 'url' parameter with format uri but no description (0% coverage). The tool description does not explicitly explain the parameter syntax or constraints beyond implying it is a TikTok video URL. While the name makes this inferable, the description itself adds minimal semantic value for the parameter, leaving a moderate gap.

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 opens with 'Fetch or generate a normalized TikTok video transcript', which clearly specifies the action (fetch/generate), the resource (TikTok video transcript), and distinguishes it from sibling tools like get_instagram_post_transcript. It further clarifies the output type ('plain text and timestamped segments'), making the purpose unambiguous.

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 clear context for when to use this tool (for TikTok video transcripts) and hints at caching behavior ('Canonical transcripts are reused'). However, it does not explicitly mention alternatives or exclusions (e.g., 'for Instagram transcripts use get_instagram_post_transcript'), so it falls short of full explicit guidance.

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