compile_and_run

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

With no annotations, the description carries full burden. It discloses the core behavior: compiles, runs, captures output and diagnostics. It does not mention side effects like file creation or cleanup, but for a compile-and-run tool this is acceptable. The description is accurate and avoids contradiction.

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?

Two sentences, front-loaded with the key action and outputs, and a concise characterization. Every word serves a purpose; no redundancy or 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?

Given the simple nature of the tool, no output schema, and fully documented parameters, the description is complete enough. It covers the result (captured outputs) and the main inputs. Missing details like system prerequisites or error handling are minor.

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 the tool description does not need to add much. The description contextualizes the parameters (e.g., stdin fed at runtime) but does not provide additional meaning beyond what each parameter's description already states. 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 tool compiles C code with Borland Turbo C and runs the resulting DOS executable, capturing stdout/stderr, exit code, timing, and diagnostics. It distinguishes from siblings like compile_check (only compilation) and run_example (runs existing examples) by emphasizing the full compile-and-run workflow as 'the everyday workhorse'.

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 implies this is the primary compile-and-run tool but does not provide explicit when-to-use or when-not-to-use guidance. Sibling tools like compile_check and run_example exist, but no context is given for choosing between them.

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