Roblox MCP

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 but fails to deliver. It does not indicate that focus operations animate the camera over time (implied only by the duration parameter), does not describe what data structure is returned for 'info' or 'suggest' actions, and does not disclose whether these changes are destructive, persisted, or temporary.

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 extremely brief (11 words) with no redundancy. However, it may be excessively terse given the tool's complexity—packing four distinct operation modes into a colon-separated list without elaboration on their differences or return behaviors.

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 polymorphic tool with 8 parameters, nested objects, and no output schema, the description is insufficient. It fails to explain what the tool returns for each action mode, does not describe the animation behavior implied by the duration parameter, and provides no context about the side effects of camera manipulation in the environment.

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 has 100% description coverage, establishing a baseline of 3. The description mentions 'by path or position' which provides semantic linkage to those specific parameters, but does not add syntax details, valid ranges, or usage examples beyond what the schema already documents.

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 lists specific capabilities (get info, focus, suggest view) but frames them as 'Camera operations' which is vague and partially tautological with the tool name 'manage_camera'. It lacks a strong, specific verb and does not clearly convey the tool's polymorphic nature (one tool that does 4 distinct things).

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 provided on when to use this tool versus alternatives, nor when to select specific action modes (info vs focus_path vs suggest). The parameter relationships (e.g., that focus_path works on selection if path is omitted) are only documented in the schema, not the description.

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