list_roblox_studios

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Lists' implies a read-only, non-destructive operation, but the description does not explicitly mention side effects, return behavior, or process scope beyond 'running.'. For a simple list tool this is reasonably transparent, though not deeply informative.

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 a single sentence with the core action front-loaded. The 'Official Roblox Studio:' prefix adds little value, but there is no wasted explanation and the length is appropriate for such a simple tool.

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 zero parameters and no output schema, the description tells the agent what the tool does well enough to invoke it successfully. It does not explain how the returned list is shaped or how it relates to selection tools like set_active_studio, but these are minor gaps for a parameterless list operation.

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 tool has zero parameters and an empty input schema, so the schema already fully defines the input contract. The description needs to add no parameter-level semantics; the baseline for a 0-parameter tool is 4.

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 uses a specific verb, 'Lists,' and a specific resource, 'all running Roblox Studio processes and open places,' so an agent immediately knows what the tool does. It is also clearly distinguishable from sibling tools like set_active_studio or get_studio_state, since this is a discovery/list operation rather than selection or state retrieval.

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 is provided about when to use this tool versus related alternatives such as get_studio_state, studio_info, or set_active_studio. The description states only what the tool does, not why an agent should choose it or when a sibling would be more appropriate.

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