get_lipsync_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only status lookup via '查', but it does not describe the return format, whether progress is a percentage/state, or whether the endpoint is safe to poll. '免费' is minor behavioral context but does not meaningfully disclose operation semantics.

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 very short and the core action is front-loaded. '免费' is extra but arguably useful. It is concise, though the brevity leaves important behavioral and usage information absent.

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 no output schema, no annotations, and no usage guidance, the description is under-specified. An agent knows it checks lip-sync progress for an episode, but not what the returned progress looks like, when to call it, or how the episode_id parameter is used. This is insufficient for confident invocation.

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 0%, and the description must compensate. It does not explain episode_id in the input schema or how to obtain it. The phrase '整集' weakly implies that the parameter refers to an episode, but the mapping to episode_id is left to inference.

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 states a clear verb and resource: '查整集口型同步进度' (check whole-episode lip-sync progress). It is specific enough to distinguish the tool from generation/execution siblings like lipsync_episode or lipsync_shot, but it does not explicitly name a competing status tool or clarify how it differs from more general status tools like get_run_status.

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?

No guidance is given for when to use this tool versus alternatives. There is no mention that it should be called after lipsync_episode, no polling guidance, and no exclusion criteria. The phrase '免费' (free) is about cost, not usage context.

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