compile_plugin

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. It does not say what happens on compilation failure (are Roslyn diagnostics returned?), whether output_path is overwritten, whether reference resolution failures are fatal, or what the response looks like. For a compile step this is a meaningful gap.

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 tight sentence with no filler and the core action front-loaded. It is not padded, but it is also thin enough that the brevity comes partly from omission rather than efficiency.

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?

With 5 parameters, 4 required, no annotations, and no output schema, the description should explain failure behavior and the shape of a successful compile result. It leaves the agent without enough context to anticipate errors or interpret success.

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 every parameter is already documented in the schema. The description adds only the Roslyn implementation detail and no additional semantics about parameter interaction (e.g., how source_files relates to managed_directory references). Baseline 3 applies.

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 a specific verb and resource: compiling a BepInEx plugin C# source file, and names the compiler (Roslyn). It is distinguishable from siblings like generate_plugin and build_and_deploy, though it does not explicitly say how it differs from them.

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 versus generate_plugin, build_and_deploy, or validate_assembly, nor any stated prerequisites. The agent must infer that this is the raw compile step from the name alone.

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