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 '添加域名' (add domain) which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether this is idempotent, rate limits, or what '请求ID' (request ID) in the return means. The description is minimal and lacks crucial operational context for a domain creation tool.

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 extremely concise with just '添加域名' (add domain) followed by parameter and return documentation. While efficient, it's arguably under-specified rather than optimally concise. The structure with Args/Returns sections is clear but minimal.

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 domain creation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after adding a domain, error conditions, or relationship to other live streaming operations. The return value '请求ID' (request ID) is mentioned but not explained. More context is needed for effective use.

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%, so the schema already documents all parameters thoroughly with descriptions, examples, and defaults. The description lists parameter names in Chinese but adds no additional meaning beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 '添加域名' (add domain) which provides a basic verb+resource, but it's vague about what type of domain (live streaming domain) and doesn't distinguish from sibling tools like 'add_delay_live_stream' or 'enable_live_domain'. The purpose is clear at a high level but lacks specificity for this context.

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 on when to use this tool versus alternatives like 'enable_live_domain' or 'add_delay_live_stream'. The description provides no context about prerequisites, when this is appropriate, or what happens after adding a domain. Usage is implied through parameter names but not explicitly stated.

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