再生開始

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

Discloses synchronous return, error code (MODE_CONFLICT), and what triggers it. No annotations for destructive/readOnly, so description provides necessary behavioral context for a state-changing operation.

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?

Two compact sentences covering purpose, behavior, and error conditions. 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?

Fully describes the tool's action, conditions, and return value. No output schema, but description mentions return fields. Sufficient for a 0-parameter tool.

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?

No parameters; description adds value beyond schema by explaining behavior and return value. Schema coverage is 100%, but description compensates by providing context not in 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?

Description clearly states it switches from Editor to Playing mode, processes at frame boundaries, and returns mode and sceneGeneration. This distinguishes it from siblings like dx12_stop (stop) and dx12_get_mode (query).

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?

Implies use for initiating play mode, with condition for unreachable states (no camera). Does not explicitly state when not to use, but context is clear enough given sibling tools.

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