merge_mesh_files

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

No annotations provided, so description must convey behavior. It states 'simple concatenation', implying no transformation, but lacks details on error handling, file validation, or whether input files are modified. Adequate for a simple operation but could be more transparent.

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?

Three sentences plus parameter descriptions. Front-loaded with main purpose, then usage guidance, then parameter details. Well structured and efficient, though the parameter section could be integrated into the paragraph.

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 tool with 2 simple parameters and no output schema, the description covers purpose, usage, and return value (dict with merge statistics). It also differentiates from sibling tool. Adequate for the complexity level, though missing edge cases.

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 description must define parameters. It provides brief descriptions: 'List of STL file paths to merge' and 'Destination path for the merged file.' This adds basic semantics but doesn't specify formats, constraints, or expected types beyond schema. Satisfies minimum but not extensive.

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?

Clearly states it combines multiple STL files into a single mesh file via simple concatenation. Specifies the resource (STL files) and the action (merge). Distinguishes from sibling tool 'merge_stl' which handles offsets.

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?

Explicitly says to use 'merge_stl' for positioning parts with offsets, indicating when this tool should be used and when not. Also mentions it's useful for composing multi-part designs, providing clear usage context.

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