geom_bake_to_static_mesh

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly mentions destructive behavior via the 'overwrite' parameter ('Delete an existing asset at asset_path first') and saving via 'save' ('Save the generated package after creation'). It also declares the return format ('Structured JSON with baked asset path and mesh counts'). This covers the main side effects and output, though it doesn't detail potential failure modes or prerequisites beyond expecting a DynamicMesh actor.

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 well-structured: a one-line purpose, a numbered list of parameters with explanations, a returns section, a KB reference, and a concrete example. Every element serves a purpose, with no fluff or repetition. The parameter list is necessary given the lack of schema descriptions, and the example demonstrates a realistic invocation.

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 complexity (8 parameters, 0% schema coverage, and an output schema already describing return structure), the description covers all necessary aspects: parameter meanings, return format, behavior (overwrite/save), and an example. It also provides a KB reference for deeper context. Nothing critical for an agent to call this tool correctly appears to be missing.

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 description coverage is 0%, so the description must compensate for all 8 parameters. It does so comprehensively: each parameter has a concise, meaningful explanation (e.g., 'enable_nanite: Enable Nanite on the generated static mesh'). This adds value far beyond the schema's bare type/default information, making the parameters self-documenting.

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 starts with a clear, specific statement: 'Bake a DynamicMesh actor into a StaticMesh asset.' This names the verb (bake), the input resource (DynamicMesh actor), and the output (StaticMesh asset), making the tool's purpose unambiguous. It distinguishes this from sibling geometry tools like geom_boolean_op or geom_remesh by focusing on the conversion to a static mesh asset.

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 implies usage for baking dynamic meshes but does not explicitly state when to use this tool over alternatives. It provides a concrete example and parameter explanations but no exclusions or comparisons to sibling tools. The KB reference hints at more context but is not directly integrated. This is implied usage rather than explicit guidance.

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