game_viewport

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

With no annotations (e.g., readOnlyHint, destructiveHint) provided, the description carries full responsibility for behavioral disclosure. It states the tool can 'create or configure', implying mutation, but does not mention reversibility, permission requirements, side effects, or return behavior.

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, focused sentence that directly states the tool's action and target. It is concise and front-loaded, with no redundant information.

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 8 parameters and no output schema, the description is insufficiently complete. It does not explain the relationship between actions and parameters (e.g., which parameters are needed for 'create' vs 'configure'), nor does it describe return values or error cases.

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 each parameter is described with reasonable detail. The tool description adds no extra semantic value beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 specifies the verb (create or configure) and the resource (SubViewport node), making the core purpose clear. However, it doesn't fully distinguish from sibling tools like 'game_set_property' or 'game_spawn_node' that could also affect viewports.

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 such as game_set_property or game_instantiate_scene. The description lacks any context about prerequisites, suitable scenarios, or when to choose a different tool.

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