join_objects

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

The description discloses that meshes remain separate inside the object, no boolean merge, and the first name becomes active object. With no annotations, this provides full transparency.

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 paragraphs, front-loaded with purpose, no fluff. Every sentence adds value, including the TIP.

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?

Even with high schema coverage, the description fully explains behavior for a simple tool, including return value. No gaps.

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?

For the single parameter 'names', the description adds 'List of object names to join. The first name becomes the active object.' This goes beyond the schema's minimal definition.

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 'Join multiple mesh objects into one' and specifies it keeps geometry as-is, distinguishing it from booltool_auto_union which performs a boolean union.

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 provides a tip to use booltool_auto_union for fusing overlapping meshes, giving clear when-not-to-use guidance and an alternative.

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