geom_remesh

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

With no annotations, the description carries the full behavioral burden, and it partially succeeds: it discloses that the actor is mutated, explains the discard_attributes destruction behavior, and states the return shape. However, it never says whether the operation is reversible/undoable, whether remeshing happens in-place on the existing mesh or creates a new object, or what prerequisites exist beyond the actor being a DynamicMesh. For a mutation tool with zero annotation coverage, these are notable gaps.

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 front-loaded with a crisp one-line purpose and follows a logical Args/Returns/KB/Example structure where each section earns its place. The parameter documentation is somewhat redundant with schema defaults but justifies itself by adding semantics. The KB reference is of marginal value to an AI agent without a retrieval mechanism, but the example is genuinely instructive.

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 values need no elaboration, and the description covers all parameters, both operating modes, and provides a worked example. It even states the actor-type prerequisite implicitly through 'DynamicMesh actor label to mutate'. The main gap is the missing disclosure of in-place mutation consequences and reversibility, which matters for a destructive geometry operation with no annotations.

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, and it fully does: all six parameters receive meaning beyond the bare schema. It clarifies the conditionality between target_triangle_count and target_edge_length ('<=0 uses triangle count mode'), explains what reproject and discard_attributes actually do, and gives the example usage. This is exemplary compensation for a schema with no descriptions.

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?

"Uniformly remesh a DynamicMesh actor" states a specific verb, resource, and scope in one sentence. Among the geometry siblings (geom_boolean_op, geom_extrude, geom_uv_unwrap, geom_apply_displacement, geom_bake_to_static_mesh), none perform remeshing, so an agent can unambiguously select this tool. The 'uniformly' qualifier adds precision about the remeshing strategy.

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 through the two-mode explanation (triangle count vs edge length) and a concrete example, but it never explicitly states when to choose this tool over alternatives or when not to use it. There are no exclusion conditions or alternative routing to sibling geometry tools. The KB reference hints at deeper guidance but isn't actionable in the description itself.

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