export_tech_pack

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

No annotations are present, so the description must disclose behavior itself. It reveals that the tool writes a tech pack to an absolute file path, but does not mention overwrite behavior, whether directories are created, side effects, or return values. This is thin for a file-creation operation.

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 short and front-loaded; the first sentence states the operation and output format, and the Args line adds the one necessary parameter detail. It is concise, though slightly under-specified.

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 export tool, the description covers the essential 'what' and 'where.' However, with no annotations or output schema, it omits usage context versus sibling exports and any return/error behavior, making it only minimally complete.

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?

With 0% schema description coverage, the description compensates by explaining file_path as 'Absolute path for the tech pack output,' adding meaning beyond the schema's bare 'File Path' label. It could specify expected extension or file-vs-directory, but the core semantic is clear.

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?

States a specific action ('Export') and a distinct resource ('tech pack'), and clarifies content ('JSON metadata and images'). It is distinguishable from sibling export_* tools by the unique 'tech pack' target, though it does not 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 on when to choose this over the many sibling export tools (export_obj, export_pattern_sheet, etc.), nor any prerequisites such as a loaded project. The description simply states what the tool does.

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