テストクライアント起動

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

Describes frame-boundary execution, error conditions if not in playing state, and the fact that it spawns a new process. Annotations are minimal (only openWorldHint), so the description adds substantial behavioral context.

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?

Concise, front-loaded, and well-structured. Every sentence adds value: purpose, prerequisite, usage hint, and follow-up. No wasted words.

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 zero parameters and the existence of an output schema, the description fully covers what an agent needs: what it does, when to use it, prerequisites, and expected follow-up operations.

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?

With zero parameters and 100% schema coverage, baseline is 4. The description confirms no parameters are needed and explains why, adding value beyond the empty schema.

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 tool launches another engine process and auto-connects to localhost for testing multiplayer features. It distinguishes itself from all sibling tools, none of which perform this action.

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?

Explicitly states when to use (while hosting), prerequisite (must be playing as host), and follow-up steps (step_frames then check status). Provides clear context for proper usage.

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