remove_procedural_mesh_component

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: partial removal (only the first component), the need for repeated calls, and the was_root flag in the response. It does not address undo/transaction semantics, so it lands just above adequate rather than exhaustive.

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?

Three sentences, front-loaded with the action before the caveats and the return shape. Every sentence carries load: the first identifies the operation, the second supplies the non-obvious semantics, the third compensates for the absent output schema.

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 one-parameter destructive tool with annotations covering safety, the description is complete: it states scope (editor world), removal semantics, and the return payload even though no output schema exists. Nothing an agent needs to invoke it correctly is 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?

There is a single parameter with 100% schema description coverage, so the schema already documents actor_label fully. The description's phrase 'named actor' corroborates but adds no format, lookup, or disambiguation detail beyond the schema, making the baseline 3 appropriate.

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 names a specific verb ('Destroy') and resource ('UProceduralMeshComponent on a named actor in the editor world'), and frames itself as the inverse of create_procedural_mesh_component, which anchors it in the mesh-component cluster. An agent can tell what it does 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?

It gives concrete operational guidance: only the FIRST matching component is removed, so actors with several need one call each, and the inverse-of-create framing signals when it applies. It stops short of explicitly ruling out alternatives such as a general remove_component_from_actor, so it is strong but not complete.

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