get_episodes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond the purpose. It does not mention pagination behavior, error handling, or rate limits. With annotations present, the description is adequate but not additive.

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 concise—a single phrase. While it states the purpose, it lacks explanatory detail such as return format or pagination. It is not wasteful, but it is under-specified for a tool with four parameters. Score 3 reflects adequate conciseness with missing 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?

Given the presence of an output schema and high parameter coverage, the description is minimally adequate. However, it does not explain the role of the 'type' or pagination parameters, nor does it address potential confusion with 'get_episode_info'. The description leaves gaps in operational understanding.

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 100%, so each parameter has a description in the schema. The tool description does not provide additional meaning beyond what the schema already offers. According to calibration, baseline 3 is appropriate when schema coverage is high.

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 indicates the action (get) and resource (episodes for an entry). However, it does not differentiate this tool from the sibling tool 'get_episode_info', which likely retrieves a single episode. The verb and resource are specific, but sibling distinction is lacking.

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?

There is no explicit guidance on when to use this tool versus alternatives like 'get_episode_info' or other 'get_*' tools. The description does not provide context for usage, such as prerequisites or scenarios. This leaves the agent without direction on selection.

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