Script / Execute

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

Annotations only say destructive/open-world/non-idempotent; the description goes far beyond by disclosing exactly what is guarded (endless loops against a time budget, runaway recursion), that the process survives failures, and precisely which spawned concurrency (Thread, Task.Run, ThreadPool) is cleaned up versus which is not (timers, async void after first await, blocked waits). It also states the failure mode ('fails with Timeout') and that leftover threads produce a warning, which is unusually honest behavioral disclosure for an execution 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?

It is front-loaded with the core purpose and modes, and nearly every sentence carries operational information (timeouts, thread cleanup, RQL encoding). The second paragraph is a dense wall of text with an unfinished sentence ('(a node, string, int, float, bool)'), and the timeout default is restated from the schema, so it is not fully tight.

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 an 8-parameter, no-output-schema execution tool this covers the essentials: what is returned (result plus Console/GD.Print output), both compilation modes, parameter passing syntax, resource limits, and concurrency cleanup caveats. An agent has enough to invoke it correctly and to anticipate failure modes without further documentation.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the RQL value grammar ({key: value}, [a, b], "text", ref("Node3D#12"), godot.find("Name")) and the rule that each named value is passed as a parameter of that value's type. That materially helps an agent construct 'parameters' correctly. Minor deduction because the argument-types explanation trails off with an incomplete parenthetical and repeats the timeout default already in the schema.

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 first clause gives a precise verb and resource: 'Compiles and runs C# in the Godot editor', then distinguishes its two operating modes (snippet with implicit usings vs. a declared class with a static method). It is immediately clear what the tool does and how it differs in effect from a build/validate tool, though no sibling (script-build, script-validate, rql-query) is named explicitly to route the agent.

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?

It gives real in-tool selection guidance: snippet vs. full class, when to set className/methodName, how isMethodBody overrides mode detection, and 'leave out keys you do not need' for parameters. It also explains when to raise 'timeout'. What it lacks is any statement of when to choose this over siblings like script-build or rql-query, so it stops short of explicit alternatives.

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