video_full

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

No annotations, so the description carries the disclosure burden; it reveals the confirmation gate and that this is a heavyweight operation not needed for normal analysis, which is the key behavioral trait. It omits what happens on oversized/failed downloads and any cost or timeout implications of pulling a full file.

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?

Three short sentences, front-loaded with the action and its restriction, then the confirmation gate, then the sibling redirect. Nothing is wasted.

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?

With no annotations, no output schema, and 0% parameter coverage, the description should say more: max_mb semantics and default-bound behavior (what happens if the video exceeds 800 MB) are entirely absent, and there is no indication of return shape for a download operation.

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%, so all three parameters are bare. The description usefully explains that confirm must be True, but 'max_mb' (default 800) is never mentioned and 'url' is only implied, leaving part of the surface unaddressed.

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?

States a specific verb+resource ('下载整片' – download the full video) and immediately scopes it ('仅在你明确要看全片时使用'), distinguishing it from the sibling video_brief which handles ordinary analysis. An agent can select between the two without opening either schema.

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?

Explicitly names the alternative ('先试 video_brief') and the condition that selects this tool (only when the full video is genuinely needed), plus a hard precondition (confirm=True). When-to-use, when-not-to-use, and the gating requirement are all present.

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