Video Fetch MCP

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

No annotations are provided, so the description carries full burden. It states the action (cancel) but lacks behavioral details: whether cancellation is reversible, if it requires specific permissions, what happens to partial downloads, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 phrase '取消下载任务', which is extremely concise and front-loaded with the core action. There is zero waste or redundancy, making it efficient for quick understanding.

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 (a mutation operation to cancel tasks), lack of annotations, no output schema, and minimal description, it's incomplete. It doesn't cover behavioral aspects, error handling, or output expectations, leaving gaps for safe and effective use by an AI agent.

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%, with the parameter 'taskId' documented as '任务ID' (task ID). The description doesn't add meaning beyond the schema, such as format examples or sourcing guidance. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is added.

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 '取消下载任务' (Cancel download task) clearly states the action (cancel) and target resource (download task). It distinguishes from siblings like 'download_video' (initiates download) and 'get_task_status' (checks status), though it doesn't explicitly differentiate them. The purpose is specific but lacks explicit sibling comparison.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., task must be active), exclusions (e.g., cannot cancel completed tasks), or relationships with siblings like 'get_task_status' for verification. Usage is implied only by the action name.

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