带宽套餐列表

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the '查询' (query) semantics are consistent with a safe, read-only operation. The description adds the operational note about filling bandwidth_num but does not disclose additional behavior such as pagination, rate limits, or pricing caveats.

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 a single compact sentence that front-loads the core action and resource, then adds the key downstream usage instruction. There is no filler, tautology, or wasted words.

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 simple two-parameter, read-only list tool with no output schema, the description is complete: it explains what is returned (bandwidth packages and prices), the filter criteria (product and country), and how to use the result (bandwidth_num for orders/upgrades). Nothing critical is missing for an agent to call it correctly.

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 parameters product and country are already fully documented in the input schema. The description only alludes to '某静态住宅产品在某国家' and the returned bandwidth value, adding no extra parameter-level meaning beyond what the schema provides.

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 a specific action ('查询') on a specific resource: bandwidth packages and prices for a static residential product in a given country. It also includes the downstream purpose ('下单或升级时把返回的带宽值填到 bandwidth_num'), which clearly distinguishes it from siblings like bandwidth_detail or 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?

The description explicitly tells the agent when the returned value matters: when placing an order or upgrading, put the bandwidth value into bandwidth_num. This gives clear usage context, though it does not explicitly name alternative tools or state when not to use the tool.

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