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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds only the 'own tasks only' scoping constraint and the fact that results are paginated; it says nothing about ordering, defaults, or what a task record contains.

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?

A single compact sentence with no waste and the key scope term (本人) front-loaded. Brevity here borders on under-specification rather than padding, but nothing is redundant.

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 no-required-param read tool with full annotation coverage and no output schema, the essentials are present. Still missing are pagination defaults, result ordering, and any indication of what the returned task list contains, which an agent would need to use it confidently.

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?

Two parameters exist with 0% schema description coverage, so the description carries the burden. '分页查询' implies page/size but does not explain defaults, the 1-100 size bound, or what happens when page is omitted; the agent gets almost nothing beyond what the parameter names already suggest.

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 specific verb (分页查询 = paginated query) and a scoped resource (本人极速去字幕任务 = my own fast subtitle-removal tasks). The '本人' scope meaningfully separates it from a general subtitle-task listing, though it never names which sibling (e.g. get_subtitle_task) handles single-task retrieval.

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 when-to-use guidance and no mention of alternatives among the eight sibling tools, despite get_subtitle_task and delete_subtitle_task being obvious neighbours. An agent must infer from the name alone that this is the listing entry point.

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