寄せて撮影

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

The description discloses that it moves camera close to entity, waits one frame, and returns a PNG image. Annotations indicate idempotentHint=true and openWorldHint=false. However, it does not specify whether the camera resets to its original position after the operation, leaving some behavioral ambiguity.

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 concise, with a single paragraph that front-loads the primary action. Every sentence serves a purpose: describing the action, input specification, use case, and output format. No extraneous text.

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 two parameters and no output schema, the description covers input usage, output format (image block + text with path/size), use context, and distinction from sibling. It is sufficiently complete for an agent to correctly invoke the 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?

Schema coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal clarification by noting they are mutually exclusive ('entity(id) か name 指定'), but this does not significantly enhance understanding beyond the 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 action: focus camera on target entity and take a screenshot, returning PNG. It distinguishes from sibling dx12_screenshot by noting that dx12_screenshot returns the active game camera image during play, while this tool uses the editor camera.

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?

The description explicitly states when to use: to visually confirm placement and appearance (配置や見た目を自分の目で確認する). It also directly contrasts with dx12_screenshot for playing game screen, providing clear guidance on tool selection.

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