mxa_set_vbw

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

The annotations provide destructiveHint: false, but the description adds no behavioral details beyond that. It does not mention state changes, side effects, or output. The description adds minimal value over annotations.

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 (one short sentence), but it is in Chinese and lacks structure. While brevity is positive, it omits necessary parameter details, making it less helpful.

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?

Given the tool has two un-described parameters and an outputs schema (unknown content), the description is insufficient. It provides no context about parameters, output, or typical usage scenarios.

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 description does not explain the two parameters ('alias' and 'params_json'). The agent has no semantic understanding of these inputs from the description.

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 tool sets video bandwidth (VBW), with a specific verb and resource. It distinguishes from siblings like mxa_set_rbw and mxa_set_band. However, the description is in Chinese, which may be a barrier for English-speaking AI agents.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor any prerequisites or exclusions.

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