Roblox MCP

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

No annotations provided, so description carries full behavioral disclosure burden. While it labels [PRO] features, it fails to disclose atomicity guarantees (critical for mass_* operations), failure modes, partial completion behavior, or what 'pivot' specifically does (CFrame transformation). Missing safety warnings for destructive operations.

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?

Extremely compact single sentence covering 12 distinct operations. Front-loaded with basic operations, with PRO operations clearly demarcated. No wasted words, though brevity may be excessive given the tool's polymorphic complexity (18 parameters with conditional requirements).

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 18 parameters and complex conditional logic (different params per action), the description is minimal but the rich schema (100% coverage with 'Used by' qualifiers) compensates. However, lacks guidance on common usage patterns (e.g., clone vs smart_duplicate) and PRO tier implications. Acceptable but minimal for this complexity level.

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?

Input schema has 100% description coverage with 'Used by' constraints documented per parameter. The description adds the [PRO] categorization which helps group the action enum values, but doesn't add syntax details, examples, or conditional requirement explanations beyond what the schema already provides. Baseline 3 appropriate for high-coverage schemas.

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?

Lists specific mutation verbs (create, delete, clone, move, rename, pivot) and identifies the resource (Roblox instances). The enumeration of structural operations distinguishes it from siblings like query_instances (read) and manage_properties (field updates), though it doesn't explicitly clarify this distinction.

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 no guidance on when to use this tool versus alternatives like execute_luau (which could script mutations) or manage_properties (for updates without structural changes). No mention of prerequisites, permissions, or PRO tier requirements despite the [PRO] label in the description.

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