Add Ip Speed Limit

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether the rule takes effect immediately, whether an existing rule for the same IP is overwritten or rejected, what units upload_kbps/download_kbps use, whether the device requires a restart, or what permissions are needed.

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?

It is short, but the brevity comes from under-specification rather than efficient packing of useful content. Nothing is front-loaded because there is nothing to load.

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 mutation tool with five parameters at 0% schema coverage and no annotations, this is completely inadequate. The output schema exists so return values need not be described, but that alone does not compensate for the missing input semantics and behavioral context.

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% across five parameters, and the description mentions none of them. It gives no meaning for ip_addr, upload_kbps, download_kbps, enabled, or comment, nor their units, ranges, or defaults.

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 '添加 IP 限速' is essentially a verbatim translation of the tool name 'add_ip_speed_limit', so it restates the name rather than adding information. It does imply a mutation on an IP-based rate limit, but says nothing about scope (per-host? per-group?), units, or what distinguishes it from add_mac_speed_limit beyond the noun.

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 when-to-use, when-not-to-use, prerequisites, or references to alternatives such as list_ip_speed_limits or delete_ip_speed_limit. The agent must infer everything from the name.

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