compose_assembly_parts

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It mentions merging and writing to a file but omits critical details: potential side effects, error handling (invalid JSON, overwriting), resource requirements, or performance implications. The behavioral description is minimal.

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 concise with three sentences that front-load the main purpose. It avoids redundancy and uses a clear docstring format. However, it could be slightly more structured (e.g., bulleted notes) without sacrificing brevity.

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's moderate complexity, the description is insufficient. It fails to explain return values, error scenarios, input constraints (e.g., required assembly state), or output file characteristics. The agent lacks guidance for robust invocation.

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 adds meaning by labeling 'assembly_json' as a JSON string of the assembly state and 'output_path' as a file path for writing. While not exhaustive (e.g., JSON structure, file format constraints), it provides adequate context beyond the bare 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 clearly states the tool's purpose: to compose all assembly parts into a single STL file by merging meshes according to their positions. It uses a specific verb ('compose') and resource ('assembly parts'), and the distinguishing detail ('single output STL file') helps differentiate it from siblings like 'compose_models' or 'compose_part_from_primitives'.

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 does not explicitly state when to use this tool relative to alternatives. It implies usage when merging assembly parts but lacks prerequisites, exclusions, or references to sibling tools like 'add_assembly_part'. There is no guidance on context or when not to use it.

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