Profile Roblox runtime

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

Annotations declare readOnlyHint: true, and the description's 'Sample' aligns with that non-mutating behavior. It adds 'locally' to clarify scope, but does not disclose details such as whether sampling affects game performance or how results are delivered. The description is consistent with annotations and adds some value beyond them.

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 a dense yet efficient list of metrics. Every word earns its place, and the structure is front-loaded with the verb and resource. No fluff or redundancy.

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 tool is relatively simple with 3 optional params and no output schema, so the description provides a decent overview. However, it omits what the tool returns and how to access the results, and it lacks usage differentiation from siblings like 'benchmark'. These gaps leave the agent without a complete picture.

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?

Schema description coverage is only 33%, with clientId described but durationMs and topClasses lacking semantic explanations. The description lists metrics like 'FPS/frame time' and 'instance class counts' that loosely relate to these parameters, but it does not explicitly map them, so the agent cannot confidently infer param meanings.

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 'Sample' and lists concrete metrics (FPS, frame time, class counts, memory, ping, physics) with the scope 'locally', clearly identifying the Roblox runtime as the resource. However, it does not explicitly distinguish itself from the sibling 'benchmark' tool, which may overlap in purpose.

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 on when to use this tool versus alternatives like 'benchmark' or 'get_game_info'. The phrase 'locally' hints at client-side use, but there are no explicit when-to-use or when-not-to-use instructions, leaving the agent to guess suitability.

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