export_mesh_tool

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 add genuine value by disclosing the `trimesh` dependency and how to install it. However, it does not say whether an existing output file is overwritten, where output lands when output_path is empty, or whether the conversion can fail on unsupported geometry.

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: the action and supported targets come first, and the dependency caveat follows. Nothing is padded and the prerequisite is not buried.

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?

An output schema exists, so return-value explanation is not required, and the format list plus dependency note cover the essentials. Still, for a file-writing tool the unspecified default output location and overwrite behavior are meaningful gaps an agent would want closed.

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%, and the description usefully supplies the accepted format values (stl, glb, gltf, ply, off) that the schema leaves as an unconstrained string with a default. It says nothing about the semantics of an empty output_path default, leaving one of three parameters unexplained.

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 verb and resource (convert OBJ to another mesh format) and enumerates supported targets, so the agent knows exactly what the tool produces. It is clearly distinct in function from siblings like preview_obj and send_to_unreal, but never says so explicitly.

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 phrase 'a rendered OBJ' implies obj_path must come from a prior render step, so usage is inferable but never stated. No alternatives are named (e.g., when to use this instead of send_to_unreal), and no preconditions beyond the optional dependency are given.

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