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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context not present in annotations: existing game references are pinned to immutable versions and other worlds' pinned versions must be preserved. Return format and pagination remain undisclosed.

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?

Front-loaded with the verb and the payload list, then adds the pinning constraint. The final clause about reading each connected game largely restates the earlier 'before editing' instruction, a minor redundancy, but the description stays short and information-dense.

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 tool with no output schema and no annotation gaps, the description is serviceable: it explains content and a real editing constraint. It is incomplete on the one thing the schema does not cover, the meaning of its two required identifiers.

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 0% for two required parameters, workspaceId and liveWorldId, and the description never explains what either identifier refers to or where to obtain it. With two undocumented params and no compensation, this falls below the baseline.

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 (Read) and enumerates the resource contents: world settings, current version, input bindings, interface source, connected games. However, it never distinguishes itself from the near-identical sibling get_experience_world, which an agent could easily confuse it with.

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?

Gives an implied workflow context ('before editing') and repeats it for connected games, which tells the agent this is a prerequisite read. It does not name alternatives or state when a sibling like get_experience_world or list_world_experiences should be used instead, leaving the routing decision to inference.

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