extract_wxapkg

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

With no annotations, the description carries full burden but only states 'Extract', giving minimal behavioral detail. It does not disclose potential side effects like overwriting, permissions required, or error handling beyond the basic action.

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 at one sentence, but this brevity sacrifices essential detail. It is not front-loaded with critical information like prerequisites or output expectations.

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?

Given the tool extracts files with two parameters and has an output schema, the description is incomplete. It does not explain the output structure, behavior on existing files, or error cases, which are important for a file extraction tool.

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%, and the tool description provides no additional meaning for the parameters. It names 'wxapkg_path' and 'output_dir' but offers no explanation of expected formats, valid ranges, or constraints beyond the schema types.

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 uses the verb 'Extract' and specifies the resource as a 'decrypted wxapkg file' and the destination 'output_dir'. It clearly distinguishes from siblings that handle decryption or inspection, though it does not explicitly differentiate from decrypt_and_extract_* tools.

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 the input must be decrypted but provides no guidance on when to use this tool versus alternatives. It does not state prerequisites, such as needing a decrypted file first, or mention conditions like file conflicts.

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