execute_lua

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

With no annotations provided, the description must disclose behavior. It states 'The code runs in the plugin context with full API access,' which conveys the powerful, potentially side-effect-laden nature of execution. It also explains how to retrieve results ('Use "return <value>" to get results back'). It does not mention error handling or safety warnings, but the 'full API access' statement effectively communicates risk.

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, front-loaded with the core action and context. Every phrase contributes: 'Execute arbitrary Luau code', 'return the result', 'plugin context with full API access', and the return-value convention. No repetition 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 tool's complexity and lack of output schema, the description adequately covers execution context and return protocol. It highlights the killer feature (full API access) and the return mechanism. It could optionally mention error behavior or that arbitrary code may have side effects, but for an execution tool, the provided information is sufficient for an agent to invoke it correctly.

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?

The input schema provides 100% coverage for both parameters ('code' and 'args'). The description adds the important convention to 'return <value>' for results, which relates to the 'code' parameter, but does not expand on 'args' beyond the schema. Since the schema already documents both parameters, the description meets the baseline without adding substantial semantic value.

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's function: 'Execute arbitrary Luau code in Roblox Studio and return the result.' It identifies a specific verb ('execute'), resource ('Luau code in Roblox Studio'), and differentiates itself from sibling tools that perform specific operations. The addition of 'plugin context with full API access' further distinguishes it as a general-purpose code execution tool.

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 usage as a flexible, arbitrary-code fallback but does not explicitly contrast it with sibling tools or provide when/when-not guidance. It states the execution context ('plugin context with full API access') and return mechanism, but lacks exclusions or alternative tool references, so usage context is implied rather than explicit.

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