execute_code

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

The description discloses security restrictions (no System.IO, System.Net, System.Diagnostics) and the auto-wrapping behavior in a static class, adding context beyond the readOnlyHint=false annotation, which already indicates mutation is possible.

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 compact, with each sentence providing distinct value — an overview, performance benefit, security constraints, auto-wrapping, and a concrete example — without unnecessary filler.

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?

The description covers core execution behavior and restrictions, but lacks explicit details about return format, error handling, and the undo_label semantics, which would be important given no output schema.

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?

With 0% schema description coverage, the description compensates for the main 'code' parameter by providing an example and explaining auto-wrapping, but it does not explain the 'undo_label' parameter.

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 'Execute C# code in Unity Editor via Roslyn' with a specific verb and resource, making the tool's function clear and distinguishable from siblings like compile_preflight or run_playtest.

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 phrase '10-40x faster than recompile' implies a use case for rapid experimentation, but there is no explicit guidance on when to prefer this over alternatives, nor exclusions.

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