find_wechat_package_roots

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

No annotations are provided, placing full burden on the description. It only states the tool finds roots for the current Windows user but does not disclose effects of the search_roots parameter, any system access details, or potential side effects. Behavior is underspecified.

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 a single sentence that efficiently conveys the core purpose. It is concise but could benefit from more structured information about parameters and output.

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?

The description is minimal and does not explain what constitutes a 'package root', how the tool determines them, or what the output represents. Even with an output schema present, the agent lacks context for correct interpretation.

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 single parameter search_roots has no description in the schema (0% coverage) and the tool description does not explain its meaning. The agent cannot determine whether it limits search, specifies directories, or modifies behavior.

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 clearly states the tool finds local WeChat Mini Program package roots for the current Windows user. It uses specific verbs and resource, and the purpose is distinct from sibling tools that decrypt, extract, or inspect wxapkg files.

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 implies usage for Windows users to find package roots, but does not explicitly state when to use this tool versus alternatives like list_wechat_apps or inspect_wxapkg. No guidance on prerequisites or exclusions is provided.

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