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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, establishing safety. The description adds behavioral detail about YouTube using existing captions. It does not disclose potential errors, rate limits, or the exact output format beyond the general list. With annotations covering safety, the description provides moderate added value.

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 concise with two sentences. The first sentence packs essential information effectively, and the second provides a usage instruction. While dense, it avoids redundancy and is well front-loaded. Minor improvement could be splitting the first sentence for readability.

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 complexity (4 parameters, no output schema), the description gives a high-level view of the output (metadata, transcript, vision description) but does not specify the structure or how parameters control output. It covers the main use case but leaves gaps for effective invocation, such as handling unsupported platforms or optional parameters.

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 4 parameters (url, language, transcribe, describe_images) with 0% schema description coverage. The description explains the output includes transcript and vision description, implicitly linking to transcribe and describe_images, but does not explain the 'language' parameter or clearly connect parameters to behavior. This falls short of compensating for the lack of schema descriptions.

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 clearly states the tool downloads a social media link and returns text context including metadata, transcript, and vision description. It lists supported platforms (TikTok, Instagram, YouTube, direct .mp4), distinguishing it from sibling tools like socialdl_download and socialdl_metadata.

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 explicit usage guidance: 'Use this to give Claude the content of a video or post the user pasted.' It also notes that YouTube uses existing captions when available. However, it does not explicitly state when not to use this tool or directly compare to siblings like socialdl_metadata for simple metadata retrieval.

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