list_packages

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

The description adds nothing beyond the readOnlyHint annotation. It does not mention what packages are returned, whether any filtering or grouping is applied, or any side effects. While it does not contradict the annotation, it provides no extra behavioral context.

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, but the brevity comes at the cost of clarity. It is front-loaded and has no wasted words, yet it fails to convey the necessary meaning of 'packages' or the tool's purpose.

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?

With an output schema present, return values need not be described. However, the meaning of 'packages' is unspecified, and there is no context about what packages are available or what the list represents. For a simple 0-param list tool, more resource context is needed for full completeness.

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?

The tool has zero parameters and schema coverage is 100%, so there are no parameter semantics to explain. The baseline for 0 params is 4, and the description does not need to address parameters.

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 '列出套餐' (List packages) is essentially a restatement of the tool name in another language. It provides no additional detail about what kind of packages are listed or how this differs from other list tools, making the purpose ambiguous.

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 gives no guidance on when to use this tool, what prerequisites exist, or how it relates to sibling list tools such as list_vpn_clients or list_wan_configs. It is a bare command with no contextual usage instructions.

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