シーン設定変更

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

The description adds behavioral context beyond annotations: partial field application, potential rebake on envMapPath change, and return value structure. This supplements the idempotentHint and openWorldHint annotations with practical runtime 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?

Two efficient sentences. First states purpose, second notes key behavior. No fluff, front-loaded with primary action.

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 setter with one nested parameter, the description covers partial update and rebake behavior. Missing explicit output schema details, but the description mentions return values for the key case. Adequate given tool complexity.

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%, but the description adds semantic context: 'only specified fields in skybox are applied' and explains the rebake trigger for envMapPath. This helps the agent understand partial updates and side effects not obvious from schema alone.

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 sets the scene's skybox/IBL settings, with specific behavior of partial field application and rebake on envMapPath change. It distinguishes from sibling tools like dx12_get_scene_settings by being the only setter for skybox.

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 on when to use this tool versus alternatives (e.g., dx12_set_post_process for other scene settings). The description does not specify prerequisites or conditions that might make this tool inappropriate.

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