Get game info

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

Annotations already establish readOnlyHint=true and openWorldHint=false. Beyond that, the description adds a meaningful operational precondition ('Requires the connected state') and enumerates the information returned, which helps the agent understand the tool's scope without an output schema. It does not explain error behavior when disconnected, but the added context is substantial.

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 two tight sentences that front-load the purpose and then state the precondition. Every listed field contributes to understanding what the overview includes, with no redundant phrasing.

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 read-only overview tool with no output schema, the description is largely complete: it specifies the contents returned and the connected-state requirement, while the only parameter is documented in the schema. Minor gaps remain around return formatting and disconnected-state behavior, but the essentials are covered.

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 coverage is 100%, and the single optional 'client' parameter is fully described in the schema, including its default behavior. The description does not add further meaning about the parameter, so a baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource ('Get an overview of the running game') and enumerates the returned data (place, server job id, local player, player list, performance metrics). An agent can distinguish this from narrower siblings like player_info or stats based on the listed contents, though no sibling is named explicitly.

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?

The description includes a prerequisite ('Requires the connected state'), which is useful context for when the tool can be called. However, it gives no explicit guidance on when to choose this overview over alternatives such as stats, player_info, or roblox_status.

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