game_process_mode

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

With no annotations (readOnlyHint, destructiveHint), the description must carry the full burden of behavioral disclosure. It fails to explain what setting the mode actually does to a node's processing, whether changes are reversible, or any side effects.

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 concise (one phrase), which is good, but it omits essential details. It is not merely concise; it is under-specified for a tool with two parameters and no output schema.

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 the tool's complexity (setting node process mode) and the absence of annotations or output schema, the description is incomplete. It does not explain what each mode means (e.g., 'inherit', 'when_paused'), leaving the agent without sufficient context to use the tool correctly.

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%, so baseline is 3, but the description's mode list (pausable/always/disabled) contradicts the schema's fuller list (inherit, pausable, when_paused, always, disabled), misleading the agent about valid values. This reduces the score.

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 clearly states the verb 'Set' and the resource 'node process mode', making the purpose clear. However, the list of modes in parentheses (pausable/always/disabled) is incomplete compared to the schema's full list, causing slight ambiguity but not enough to lower the score further.

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 game_pause or game_time_scale. There is no context about prerequisites or scenarios where this tool should be avoided.

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