build_package

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

With no annotations, the description carries the full burden, and it does disclose one non-obvious behavior: tuning XML automatically gains a companion SimData when its class needs client-binary data. It says nothing about overwrite semantics for an existing output package, failure behavior, or whether directories are created.

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?

Two short sentences, front-loaded with the core action, with no filler. The second sentence about SimData is a useful qualifier rather than padding; the odd line break is cosmetic.

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 two-parameter build tool with no annotations and no output schema, the description covers inputs and one important side effect but omits output/return behavior, overwrite rules, and error conditions. Adequate to attempt a call, not complete enough to predict the result.

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 coverage is 0%, so the description must compensate. It explains what project_dir should contain, which is genuine added meaning, but output_package_path gets no treatment at all (overwrite, must-exist, extension handling), leaving half the parameters undocumented.

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 gives a specific verb ('Compile') and resource ('a project dir ... into a package') and enumerates the accepted input artifacts (XML + .stbl.json + .bin/.tgi). It never names or contrasts a sibling such as validate_and_build_ts4script or compile_tuning_with_simdata, so differentiation is left to the agent.

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?

There is no statement of when to use this tool versus the closely related build/compile siblings, and no prerequisites (e.g., whether the project must be validated first). The only implied usage is 'you have a project dir and want a package.'

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