ue_compile_blueprint

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool compiles and saves, but lacks details on whether overwriting occurs, error handling, or if it returns compilation results. This is minimal for a potentially destructive write operation.

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 extremely concise with two short sentences, front-loading the core action and usage hint. No superfluous 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?

Given the tool's complexity (compile-and-save with one parameter and no output schema), the description does not cover important details like compilation error reporting, success/failure feedback, or prerequisites. It is incomplete for an AI agent to use safely.

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 one parameter ('blueprint_path') with 0% description coverage, and the tool description does not explain the expected format or meaning beyond the parameter name. The agent gains no additional insight from the description.

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 tool compiles and saves a Blueprint, specifying the verb (compile/save) and resource (Blueprint). It is distinct from siblings like 'ue_live_compile' which likely compiles without saving, and 'ue_save_all' which saves all assets.

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 advises using after manual modifications in the editor, providing a usage context. However, it does not mention when not to use it (e.g., for automatic changes) or explicitly name alternatives like 'ue_live_compile'.

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