get_episodes

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

With no annotations, the description must disclose behavioral traits. It does mention the output fields, which helps set expectations, but it does not mention pagination behavior (page/per_page) or any prerequisites beyond providing a content_id. It doesn't contradict any annotations since none exist, but it leaves some behavioral gaps.

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 concise sentences, front-loaded with the essential purpose and followed by a focused list of return fields. No redundant or unnecessary information is present.

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 3-parameter tool with no output schema, the description lists all key return fields, which is helpful. However, it stops short of explaining how pagination works or how episodes are ordered, which would make it more complete. Overall, it covers the main use case adequately.

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%, so the baseline is 3. The description adds context about content types and platform, but it doesn't significantly enrich the meaning of parameters beyond what the schema already provides. The schema already defines content_id, page, and per_page well.

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 function with a specific verb ('Get') and resource ('episode list'), and specifies the content types and platform ('specific drama, anime, or variety show on WeTV/Tencent Video'). It also lists the returned fields (episode numbers, names, durations, air dates, play links with subtitle info), which differentiates it from siblings like get_content_detail.

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 context for use: retrieving episodes for a specific show, which implies it should be used when episode details are needed. It doesn't explicitly mention alternative tools or exclusions, but the stated scope is sufficient to guide an agent in most cases.

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