godot_generate_procedural_mesh

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

Annotations are minimal (no readOnly, destructive, or idempotent hints), so the description carries the burden. 'Generate' implies creation, but it doesn't disclose whether the operation is idempotent, what happens to existing nodes with the same name, or whether it saves to disk (save_to_resource_path suggests that). It also doesn't mention whether existing meshes are overwritten or if it modifies the scene.

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 a single sentence, concise and front-loaded with the core purpose. No redundant or unnecessary text. It is appropriately minimal for the tool's complexity.

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 (multiple mesh types, optional parameters) and the presence of an output schema (not detailed but implied), the description is somewhat thin. It doesn't explain the different mesh types (grid, prism, pyramid, custom_vertices) or how to set them up, but the schema provides parameter names and simple descriptions. An agent might need to inspect the schema to fully utilize the tool, but it's adequate for basic 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?

Schema description coverage is 0%, but the schema itself provides detailed descriptions for each parameter (e.g., size, mesh_type, subdivisions). The description only mentions 'custom procedural 3D meshes' without adding any parameter-specific meaning. Since the schema is self-documenting, the description adds little beyond what's already there, but it doesn't harm.

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 states a specific action ('Generate custom procedural 3D meshes') using a specific tool (SurfaceTool). It distinguishes the tool from siblings like godot_create_csg_shape, which creates CSG shapes, by focusing on procedural meshes. However, it doesn't detail the mesh types supported, relying on the schema for that.

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 generating procedural meshes but does not explicitly state when to use this tool over alternatives like godot_create_csg_shape or godot_instantiate_model. The sibling context is clear but no exclusions or conditions are provided.

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