Ytdlp Check Archive

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about operating under a configured filesystem policy and the fact that it does not resolve URLs, which goes beyond what annotations provide. No contradictions.

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, front-loaded with the main purpose, and includes a clarifying negative statement. Every sentence earns its place with no redundancy.

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?

The description covers the core behavior and limitations, and annotations cover safety. However, the lack of parameter descriptions leaves a gap in completeness. The output schema exists but is not shown, so the agent relies on description for parameter meaning, which is insufficient.

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 0%, meaning no parameter descriptions in the schema. The tool description does not explicitly describe the 'entry' and 'archivePath' parameters. It hints at 'archive entry string' and 'archive file' but does not directly map them to the parameters. This is insufficient for an agent to understand how to use the parameters correctly.

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's purpose: checking whether an exact yt-dlp archive entry string exists in an archive file. It also explicitly states what it does NOT do (resolve URL to archive ID), which helps distinguish it from related tools like ytdlp_probe_url. The verb 'check' and the resource 'archive entry' are specific.

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 gives a clear negative guideline (does not resolve URL), implying when not to use it. However, it does not explicitly mention alternative tools or provide positive usage context. It is still clear enough that an agent can infer the tool is for existence checks only.

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