remove_render_target_2d

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

Annotations already declare destructiveHint, idempotentHint and non-readOnly, but the description adds substantial context beyond them: it loads and type-verifies before deleting, returns deleted:false plus a `note` on wrong-type or missing path rather than throwing, and is safe to re-run. It also discloses the return shape, which no output schema provides.

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?

Front-loaded with the action and scope, and every sentence carries information (safety rationale, error behavior, siblings, return shape). It is somewhat long and dash-heavy, but there is little outright waste.

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 no output schema, the description supplies the safety profile, the failure semantics, the sibling alternatives, and even the return shape, so nothing an agent needs to call 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?

Schema coverage is 100% and the single asset_path parameter is fully documented in the schema with an example path. The description adds no syntax or format detail about the parameter beyond noting that a missing path yields deleted:false, so the standard baseline of 3 for schema-carried params applies.

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 verb (Delete) and resource (render target asset) and explicitly positions itself against siblings: it names the generic delete_asset it is safer than and lists the typed sister tools. An agent can distinguish it from remove_render_target_2d_array or remove_render_target_cube without reading any 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?

Explicit when-to-use guidance: use this over delete_asset when you want the type-verified, render-target-specific deletion. It clarifies the precondition (target must actually be a UTextureRenderTarget2D) and routes to alternatives by type.

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