apply_material_to_blueprint

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

Without annotations, the description carries full burden for behavioral context. It does not disclose whether the operation modifies the Blueprint asset permanently, if it requires a specific editor state, or what happens on failure. The tool likely has side effects, but they are unmentioned.

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?

The description is a single sentence, which is efficient but overly brief. It omits essential details, sacrificing informativeness for brevity. A minimally complete description would require more structure and content.

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?

Given the tool has 4 parameters, no parameter explanations, and no usage context, the description is severely incomplete. It fails to convey what materials are acceptable, how component names are resolved, or any output behavior (though output schema exists).

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?

The input schema has 4 parameters with 0% description coverage. The description adds no information about what 'material_path', 'material_slot', 'blueprint_name', or 'component_name' mean or how to specify them correctly. This is a critical gap for correct invocation.

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 clearly states the verb 'apply' and the resource 'material to a Blueprint component', specifying the target. It distinguishes from the sibling 'apply_material_to_actor' by focusing on Blueprint components, but does not explicitly mention this distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'apply_material_to_actor' or other material-related tools. There is no indication of prerequisites, typical use cases, or scenarios where this tool is inappropriate.

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