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

Beyond the safety assurances provided by the 'readOnlyHint' annotation, the description adds important behavioral context by clarifying that it returns multiple types of assets, including 'no-watermark' and 'watermarked' addresses. This guides the agent on the nature of the output data, enhancing 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 extremely verbose, primarily due to the long list of trigger phrases, which unnecessarily bloats the definition. While this ensures high recall, it significantly harms the structural efficiency and conciseness of the tool documentation.

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 that there is no output schema, the description is highly complete in describing the functional output, specifying three distinct types of addresses (download, playback, cover image). This level of detail ensures the AI agent has all necessary context to understand the successful completion of the task.

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?

Since the schema coverage is 100%, the description primarily repeats the basic function of the 'url' parameter. It does not add any additional constraints or semantic meaning to the parameter usage beyond what the structured schema provides.

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 tool purpose is perfectly clear: it resolves TikTok URLs to return multiple asset types (download, playback, and cover images). It specifies exactly what is the outcome of the resolution process, making its intent unambiguous.

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 serves as an exhaustive list of high-intent trigger phrases that clearly define when to use the tool. Furthermore, it explicitly instructs the agent to trigger the skill even if 'Nexscope' is not mentioned, leaving no ambiguity about usage conditions.

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