Tencent Cloud Live MCP Server

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

No annotations are provided, so the description carries full burden. It states the tool deletes a domain, implying a destructive mutation, but lacks critical behavioral details: whether deletion is permanent/reversible, required permissions, rate limits, error conditions, or what '请求ID' (request ID) in returns signifies (e.g., async operation).

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 brief and front-loaded with the main purpose ('删除域名'), followed by parameter and return sections. However, the Args/Returns formatting in Chinese is slightly redundant with the schema, and more context could be added without sacrificing conciseness.

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 destructive tool with no annotations and no output schema, the description is incomplete. It doesn't explain the return value ('请求ID') meaning, error handling, or safety considerations (e.g., confirmation prompts, dependencies). Given the complexity of deletion operations, more behavioral context is needed.

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 100%, providing clear parameter details (domain_name as string with example, domain_type as integer with values 0/1 explained). The description adds minimal value by listing parameters in Chinese but doesn't enhance semantics beyond the schema's thorough documentation.

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 states the action ('删除域名' meaning 'delete domain') and specifies it's for live streaming domains, distinguishing it from non-live domain tools. However, it doesn't explicitly differentiate from sibling deletion tools like delete_live_pull_stream_task or delete_live_transcode_rule, which target different resources.

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 provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., domain must exist or be disabled), exclusions, or comparisons with sibling tools like forbid_live_domain (which might disable rather than delete).

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