bandwidth_detailRetrieve details of purchased bandwidth for a sub-account, including remaining validity period. Specify product type and sub-account ID to get current bandwidth status.
查询子账号剩余有效期内已购带宽的详情。后端缓存 120 秒，不要频繁调用。
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | 产品：static-standard=静态住宅（非原生），static-native=静态住宅（原生），static-isp-native=静态住宅（运营商原生） | |
| subAccount | Yes | 子账号 id |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
注释已提供readOnlyHint、idempotentHint等安全属性，但描述额外披露了“后端缓存120秒”这一行为特征，让代理意识到结果可能不是实时且需控制调用频率，这超出了注释提供的信息，增加了透明度。描述没有与注释矛盾。
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?
描述仅一句，长度适中，且将核心功能“查询详情”和关键限制“缓存120秒”都包含在内，没有冗余。虽然缺少结构化分点，但内容精炼，信息密度高，评分4。
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?
工具简单，仅两个参数且均必填，无输出模式，描述已涵盖功能范围、缓存行为，对于代理正确调用已足够。缺少返回格式说明，但鉴于工具简单，这不构成重大缺失，评分4。
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?
输入模式对两个参数（product、subAccount）的描述覆盖率100%，枚举值和子账号含义均已清晰说明。描述文本并未额外补充参数细节，但也没有遗漏，基线3分合适，因为模式已经承担了主要解释工作。
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?
描述明确指出“查询子账号剩余有效期内已购带宽的详情”，动词“查询”和资源“已购带宽”清晰，且限定“子账号剩余有效期”这一范围，与兄弟工具如bandwidth_package_list（套餐列表）和bandwidth_trend（趋势）有明显区别，能帮助代理准确判断功能边界。
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?
描述仅提到“后端缓存 120 秒，不要频繁调用”，这是频率限制而非使用场景指导，没有说明在何种情况下应选用此工具而非其他带宽相关工具。虽然缓存信息暗示了调用时机（不适合频繁查询），但缺少明确的正面使用条件或备选工具指引，因此得分较低。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.