bulk_compile_blueprints

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

With no annotations, the description carries full burden. It discloses return structure ('per-path success/failure plus aggregate counts') and error handling behavior ('continue_on_error' stops at first failure). It does not cover potential side effects, but compilation is generally non-destructive.

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 two sentences long, front-loaded with the core purpose, and contains no redundant information. Every sentence adds value.

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 no output schema, the description's mention of return shape and error handling is helpful. It covers key behavioral aspects, though it omits edge cases like path validation or skip-if-up-to-date. Overall complete for the tool's simplicity.

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 baseline is 3. The description summarizes the parameter shape ('paths list + continue_on_error') but does not add meaning beyond what the schema already provides.

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 'Recompile multiple Blueprints in one MCP call,' specifying the verb and resource. It distinguishes itself from the single-compile sibling 'compile_blueprint' and aligns with the bulk_*_assets family.

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 notes it is 'Useful after batch-mutating BPs via execute_unreal_python or other tooling,' providing context. Although it does not explicitly name alternatives, mentioning the bulk_*_assets family and composing compile_blueprint implies when to use this tool over single compilation.

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