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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the operation does not refund credits already deducted, which is a consequence an agent must surface before calling. It does not describe post-delete state or error behavior.

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?

Two tight clauses separated by a semicolon, front-loaded with the action and immediately followed by the consequence. Nothing is padded, though the lack of any structural marker for the credit warning is a minor nit.

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 one-parameter destructive tool with annotations covering safety and no output schema, the description covers the main risk (no credit refund). What is missing is the taskId semantics and any note on what remains queryable after deletion, leaving the agent unable to confirm it is passing a valid id.

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 single parameter taskId has no description anywhere. The description only implies the id refers to the caller's own subtitle-removal task; it gives no format, source, or how to obtain a valid id (e.g., from list_subtitle_tasks), so it fails to compensate for the coverage gap.

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?

States a specific verb-resource pair ('删除...极速去字幕任务') and scopes it to the caller's own tasks ('本人'), which cleanly separates it from the read-oriented siblings (get_subtitle_task, list_subtitle_tasks). It does not name any sibling directly, so it falls short of a 5.

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?

Usage is implied rather than stated: the ownership qualifier and the credit warning hint at when this is worth doing, but there is no explicit when-to-use, when-not-to-use, or alternate tool (e.g., a cancel/regenerate path) named. Adequate but with clear gaps.

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