create_procedural_mesh_component

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

Annotations already declare idempotentHint, destructiveHint and readOnlyHint, but the description adds real value by explaining the idempotency mechanism ('reuses the actor's existing PMC if found') and by specifying the return shape inline despite there being no output schema. It stops short of describing what happens when the actor label collides with an actor lacking a PMC, but this is solid beyond-annotation detail.

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 tightly written sentences: the action and scope are front-loaded, then idempotency, then the return contract. No filler or redundancy.

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?

For a mutation tool with full annotation coverage, a fully described schema, and an inline return description standing in for the missing output schema, the definition is nearly complete. The only gap is edge-case behavior when an existing actor matches the label but has no PMC, or when location is ignored on reuse.

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 100%, so the baseline is 3, but the description adds semantic meaning: 'reuses the actor's existing PMC if found' implies actor_label acts as the lookup key that determines whether an existing actor is reused. That clarifies the role of the required parameter beyond the schema's 'Editor label for the new actor'.

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 compound action (spawn a bare AActor, attach a UProceduralMeshComponent as root) with precise resource names. It clearly distinguishes itself from siblings like create_procedural_box_mesh and create_procedural_grid_mesh, which build geometry rather than the component host. An agent can identify the tool's role without opening the schema.

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?

Usage is only implied by the verb and the idempotency note; the description never states when to reach for this versus create_procedural_box_mesh/grid_mesh (the obvious alternatives for common cases) or what prerequisites exist. It gives useful context but no explicit when/when-not routing.

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