list_predefined_packages

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

描述清楚是只读查询操作，返回分组和尺寸重量信息，但未提供输出格式、权限要求或速率限制等额外行为信息（无标注）。

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?

两句话，简洁明了，核心信息前置，无冗余。

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?

对于简单的列表工具，描述涵盖了用途、返回内容和用例，但缺少分页或排序说明，不过不影响基本使用。

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?

输入模式无参数，描述覆盖100%且无需额外语义，基础分4。

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?

明确指明工具用于查询承运商预定义包裹列表，返回按承运商分组的尺寸和重量信息，与自定义包裹的列表（如list_packages）区分开来。

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?

提到用户可通过carrier_package_id直接引用预定义包裹以简化发货，但未明确说明何时不应使用或列出替代工具，如create_package。

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