system_create

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

No annotations are provided, so the description carries the full burden. It discloses meaningful behavioral traits: 'atomic verified transaction', 'complete multi-file', and the specific component types created. However, it does not explain what 'verified' means, whether an existing system is overwritten, or what side effects or failures might occur, leaving gaps in behavioral transparency.

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?

A single, information-dense sentence that front-loads the core action and lists the key components without wasted words. The [HIGH_LEVEL] prefix adds a useful orientation marker, and every clause contributes meaning.

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 high-complexity tool creating multiple files atomically, the description covers the overall behavior and component list, and the schema covers parameters fully. However, it omits preconditions, conflict-handling when the system name already exists, and what 'verified' entails in practice, making it minimally viable but not fully complete.

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 already documents all five parameters with 100% coverage, which earns a baseline of 3. The description adds value by mapping its listed component types (ServerScript, ModuleScript, Client LocalScript, RemoteEvents) to the schema's serverCode, moduleCode, clientCode, and remotes parameters, giving the agent a clearer mental model of how the parameters relate.

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 states an explicit verb ('Creates') and a specific resource: a multi-file Roblox modular system composed of ServerScript, ModuleScript, Client LocalScript, and RemoteEvents. It also distinguishes itself from sibling tools like system_modify and system_remove by making 'Creates' the primary action.

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?

Usage is implied by the verb 'Creates' and by the sibling-tool context (system_modify, system_remove), but the description gives no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer it is for initial system creation, but the description does not spell out the decision boundary.

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