Set Web Ports

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. It implies a mutation to the management interface but says nothing about consequences — changing web ports can drop the admin session, require reconnection on the new port, or lock out management access. That risk is entirely undisclosed.

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 a single phrase with no waste and nothing to trim, which is structurally clean, but it is too thin to earn more — conciseness paid for by omission of everything an agent needs.

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 zero annotations, an existing output schema, and fully documented params, the description is still missing the operational context an agent needs: that this alters the management access path and may disrupt the current session. It is not adequate for a settings-changing operation.

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 http_port, https_port, and force_https are fully documented (including defaults) in the schema. The description adds no interpretation or interaction between them, so baseline 3 applies.

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 ('设置 Web 管理端口') states a verb and resource, so the purpose is discernible, but it essentially restates the title 'Set Web Ports' with only the addition of '管理' (management). It gives no scope or differentiation beyond the name itself.

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?

There is no guidance on when to use this tool, no prerequisites (e.g., admin privilege), and no mention of alternatives such as set_wan_web_access or enable_ssh. The agent must infer all usage context.

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