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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions that the code must return values and that the connector serializes them, but it does not disclose potential side effects of executing arbitrary code in the client, such as state modification or crash risk, nor does it state any permission requirements. This is a significant gap for a code-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?

The description is two sentences, with the purpose stated first and usage guidance second. No filler or redundancy – every sentence contributes.

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 a tool that executes arbitrary code, the description leaves out important context such as error behavior, side effects, and what happens if the code does not return values. While the schema covers parameter details, the description alone is not complete enough for an agent to safely invoke this tool without additional assumptions, especially with no annotations or 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?

Schema description coverage is 100%, so the schema already fully documents all four parameters. The description adds no new parameter-level meaning beyond reiterating the return-value requirement for the code parameter, which is also in the schema. Baseline 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 executes Luau in the active Roblox client and returns serialized raw Lua values, which distinguishes it from exploration-only tools like search-instances. However, it does not differentiate itself from the similarly named 'execute' siblings, which may also run code in the client, leaving some ambiguity.

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 explicitly tells the agent to prefer specialized tools (search-instances, get-descendants-tree, get-script-content, script-grep) for exploration, and to use this tool only for small, targeted value probes. This gives clear when-to-use and when-not-to-use guidance for the exploration category, though it omits guidance about the 'execute' and 'execute-file' siblings.

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