studio_create_instance

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

The description implies a write operation but offers no details about side effects, permissions, error cases, or the meaning of 'allowed'. With no annotations, the agent gets minimal behavioral context.

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 single sentence is extremely brief but omits critical information. It is under-specified rather than concise, failing to earn its place by adding sufficient value.

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?

The description is severely incomplete. It does not explain the domain (Roblox Studio), what 'allowed' means, the return behavior, or how to use the parameters. For a 4-param tool with no output schema, this is inadequate.

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 0% schema description coverage, the description must clarify parameters, but it only hints at parentPath. No explanation of className, name, or properties (an object) is given, leaving the agent to guess.

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 a clear verb ('Create') and resource ('Instance class'), and hints at constraints ('allowed'). It distinguishes from deletion and finding tools, but lacks specificity about what 'Instance class' means and where it is created.

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?

No guidance on when to use this tool versus siblings like studio_find_instances or studio_delete_instances. No prerequisites or exclusion criteria are provided.

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