ue_material

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

No annotations are provided, so the description carries the full behavioral burden and provides none of it. It does not disclose that the create_* and set_* actions mutate project assets, whether those writes are destructive or reversible, what permissions are needed, or what a call returns.

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?

A single terse line, front-loaded with the resource and then the operations, with no filler sentences. It is efficient, though the brevity reflects under-specification rather than disciplined concision.

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 two-parameter dispatcher with a free-form nested params object, no annotations, and no output schema, the description is far too thin. An agent knows the action names but not what shape params must take for any of them, which is the minimum needed to invoke it correctly.

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 0% and the 'action' string has no enum, so the enumerated action names are genuinely useful parameter information that the schema does not provide. However, the nested 'params' object — which must carry different arguments per action — is completely unexplained, leaving the harder half of the call undocumented.

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 states the resource ('Materials and instances') and enumerates six concrete operations, so an agent can tell this is the material authoring/querying surface rather than ue_world, ue_blueprint or ue_media. It lacks a single unifying verb ('manage'/'author'), but the action list makes the domain unambiguous.

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 guidance on when to use this tool versus siblings, nor when to prefer create_material over create_instance, nor any prerequisites (e.g. asset must exist before set_parameter). The action list implies what is possible but says nothing about selection criteria or ordering constraints.

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