parse_unityfs

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

With no annotations provided, the description carries full burden and does well: it explains the decompression process, the location of the directory within decompressed blocks, and the special handling of decompress_block=-1. It also details the return structure. However, it could mention potential failures or permission requirements.

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 well-structured with separate paragraphs for overview, technical details, args, and returns. It is informative without excess verbosity, though a slightly more condensed initial sentence could improve conciseness.

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 no output schema and no annotations, the description is remarkably complete: it explains the algorithm, the role of different KSY files, parameter behavior, and the exact return format with nested fields. An agent can use this tool confidently without external documentation.

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 input schema has zero description coverage, but the description fully explains each parameter: path (file to parse), ksy_path (optional path, default bundled .ksy, and variants), and decompress_block (index, default 0, meaning, and -1 to skip). This adds significant meaning beyond the schema.

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 parses UnityFS/Addressables bundles, decompresses them, and re-parses the directory. It specifies the resource type and action, but does not explicitly distinguish from sibling tools like parse_with_format, which slightly reduces clarity.

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 explicit guidance on when to use this tool versus alternatives (e.g., parse_with_format, diff_parses). The description implies it's for UnityFS bundles but does not state when not to use it or provide context for sibling selection.

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