roblox_luau

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

Annotations already flag destructive=true and non-idempotent, and the description reinforces this with 'Arbitrary code may mutate the game'. It adds genuinely new behavioral context beyond annotations: 'no automatic retries', so the caller must handle failure itself, and 'Return compact aggregates', which hints at response shape.

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?

Five telegraphic clauses, front-loaded with the core action and scope, and every clause carries information (context modes, precondition, risk, retry policy). Style is terse rather than padded, though the fragmentary phrasing slightly hurts readability.

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 destructive, non-idempotent code-execution tool with no output schema, the description covers the key gaps: execution context, prerequisite ID, mutation risk, and no-retry behavior, plus a note on return shape. Missing only guidance on which sibling to prefer and any sandboxing or size semantics for 'code'.

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 schema description coverage at only 33%, the description must compensate, and it partially does: it clarifies studio_id must be the official IDE/plugin ID (reinforcing the schema hint) and enumerates the Edit/Server/Client execution contexts. But the most important parameter, 'code', gets no semantic detail beyond the 200k length cap, so the compensation is incomplete.

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?

States a specific verb (Execute) and resource (Luau code) and names the three datamodel contexts (Edit/Server/Client), which maps directly to the datamodel_type enum. However, it does not distinguish itself from close siblings like roblox_script or roblox_edit, leaving the agent to guess which execution tool to pick.

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?

Provides one hard prerequisite ('Official studio_id required') that routes the agent through roblox_studio first, and implies a raw code-execution use case. But it offers no explicit when-to-use vs alternatives among the seven siblings, nor any exclusion criteria.

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