build_target

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

No annotations are present, so the description must fully disclose behavior. It only says 'compiles the project's C++ code' without explaining potential side effects like overwriting build outputs, build duration, dependencies, or failure modes. This is a significant gap for a build/mutation tool.

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 short and to the point, but contains redundancy: 'Build a C++ target using UnrealBuildTool' and 'Compiles the project's C++ code' essentially restate the same idea. It could be condensed to one sentence without losing clarity.

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 non-trivial build tool with four parameters and no output schema or annotations, the description is under-specified. It omits important context such as build output, typical execution time, or how it differs from sibling tools like build_cook_run, making it insufficient for an agent to fully understand the tool's role.

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 already provides complete descriptions for all four parameters (clean, target, platform, configuration) with 100% coverage. The description adds no extra parameter-level context, so the baseline score of 3 is appropriate.

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 'build' and the resource 'C++ target' using UnrealBuildTool, specifically differentiating it from sibling tools like build_cook_run which also cook/run. It precisely conveys what the tool does.

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 provides no guidance on when to use this tool versus alternatives such as build_cook_run or clean_project. There is no mention of typical use cases, prerequisites, or scenarios where another build-related tool would be more appropriate.

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