set_material_usage_flag

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

Goes beyond annotations by disclosing that the flag is persisted to disk, that the engine setter no-ops when the flag already matches (explaining already_set), and that shaders are recompiled as a side effect. That shader-recompile warning is exactly the kind of costly side-effect note annotations cannot convey, though permissions/auth and reversibility are not covered.

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 operation, then idempotency semantics, then the side effect, followed by a compact return-shape block. No wasted sentences; every clause carries information.

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?

With no output schema, the explicit Returns block is a valuable addition, and the description covers persistence, idempotency, and the recompile side effect for a mutation tool. It remains slightly incomplete on usage routing and failure/permission conditions.

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 100%, so the schema already documents material_path format, the optional MATUSAGE_ prefix for usage, and the enabled default. The description adds nothing param-specific beyond what the schema provides, so the baseline of 3 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 (enable/disable) plus resource (usage flag on a UMaterial asset) and even the underlying type (EMaterialUsage), with the added scope of persisting to disk. It is clearly distinct from the obvious getter siblings like get_material_usage_flag, though it never names an alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no routing to the get counterpart (get_material_usage_flag). Context is implied only through behavioral description, not framed as usage guidance.

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