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

Annotations already declare openWorldHint=true and readOnlyHint=false; the description usefully clarifies what the caller receives (two download variants, playback address, cover image), which matters since there is no output schema. It does not disclose link expiry, rate limits, or authentication/failure behavior for what is flagged as a non-read-only, open-world call.

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 first sentence is front-loaded and efficient, but the trigger list is heavily padded with near-duplicate phrases ("TikTok video download" repeated three times, "no watermark TikTok video" vs "TikTok no watermark video"). The retrieval-keyword bulk dilutes otherwise clean structure.

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?

For a single-parameter resolver with no output schema, the description covers purpose, expected return contents, and usage context adequately. Remaining gaps (link lifetime, whether watermarked and clean URLs are always both present) are minor for a tool this simple.

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%, and the schema itself documents both accepted URL formats and the 1000-character limit. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 ("Resolve") and resource (TikTok video URLs) and enumerates the three artifacts returned: no-watermark/watermarked download addresses, playback addresses, and cover images. This distinguishes it from analytics/search siblings, though no sibling is named explicitly to disambiguate from tools like nexscope_tiktok_video_search.

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?

Gives clear context for when to invoke (saving promotional assets, offline analysis) and adds an explicit fallback trigger ("Even if the user does not explicitly mention Nexscope"). No when-not-to-use case or named alternative is provided, which keeps it from a 5.

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