fgui_get_package_info

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

There are no annotations, so the description carries the behavioral disclosure burden. '获取' and 'Returns' indicate a read-only query, and the description does state the key return content. However, it does not disclose failure behavior, dependencies, or whether the package must already be loaded.

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 compact and front-loaded with the main purpose, followed by a concise Args/Returns structure. The Args section is slightly redundant with the schema, but there is no padding or irrelevant detail.

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 one-parameter read operation with an output schema, the description is minimally adequate. However, the absence of annotations, lack of usage boundaries, and no mention of package-loading prerequisites or error behavior leave meaningful gaps for an agent selecting among many sibling tools.

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%, so the description must compensate. The Args line 'package_name: 包名称' merely restates the property name and title; it adds no format, identifier convention, examples, or additional constraints.

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 ('获取') and a specific resource ('指定 UI 包的详细信息'), and adds that the return includes all resource lists. This differentiates it from list-level siblings like fgui_list_packages, though it does not explicitly name any sibling.

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 guidance is provided about when to use this tool versus alternatives such as fgui_list_packages or fgui_list_resources. There is also no mention of prerequisites like whether a project or document must be open/loaded before calling it.

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