extract_douyin_text

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that cloud mode requires SILICONFLOW_API_KEY and that local mode is an optional offline mode. However, it omits other important behavior such as extraction output format, failure conditions, or limits.

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 short clauses and is front-loaded with the core action before mode details. It is concise, though its extreme brevity reflects under-specification rather than optimal restraint.

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 five-parameter tool with no annotations and 0% schema description coverage, the description is incomplete. Output schema exists, so return values need not be explained, but parameter meaning and usage context are still missing.

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% for five parameters, so the description must explain them. It loosely maps to asr_mode's cloud/local values but never names or explains share_link, context, asr_mode, or local_model. The compensation is far from sufficient.

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 says '提取文案' (extract text/copy), which gives a verb+object but does not specify that it extracts text from a Douyin share link. It does not distinguish this tool from siblings like recognize_audio_file or parse_douyin_video_info. The mode note helps but remains vague about the exact resource.

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?

It mentions cloud vs. local mode and the API-key requirement for cloud, but gives no guidance on when to choose this tool over alternatives. No when-to-use or when-not-to-use guidance is provided relative to sibling tools.

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