draw_material_to_render_target

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

Annotations already flag destructiveHint=true and non-idempotent. The description adds real value beyond them by disclosing the failure conditions (a non-rendering process such as -nullrhi/commandlet, or a render target lacking a resource) and the drawn flag. It stops short of explaining the destructive overwrite of the target's existing contents, which would reconcile the annotation fully.

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 tight sentences: purpose first, then failure conditions, then a compact return shape that usefully substitutes for the absent output schema. 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 simple render-target draw with full schema coverage and a safety-carrying annotation set, the description is nearly complete, covering both failure modes and the return shape. It omits whether the destination target's prior contents are overwritten and any precondition (e.g., valid/streamed assets), which is a minor gap.

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% with only 2 parameters, both already described in the schema, so the baseline is 3. The description adds no parameter meaning (no path format, no asset-validation notes) beyond what the schema provides.

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 concrete verb+resource pair ('Render a material full-screen quad into a render target'), which is specific enough to visualize the operation. The 'full-screen quad' phrasing implicitly distinguishes it from the sibling draw_material_to_render_target_region, but no sibling is named explicitly, so an agent must still infer the boundary itself.

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 gives operational context about when the draw fails, which helps an agent judge feasibility, but never addresses when to choose this tool over alternatives like draw_material_to_render_target_region or draw_texture_to_render_target. Usage is only implied, not stated.

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