ue_viewport_diff

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

The description adds behavioral context beyond annotations: it captures two snapshots with a delay (controlled by delay_ms) and returns a diff. This aligns with readOnlyHint and idempotentHint. No contradiction.

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 two sentences, short and front-loaded. The first sentence explains the action and result, the second gives a use case. 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?

Given the single optional parameter, rich annotations, and existing output schema, the description covers purpose, usage context, and behavioral key points. No gaps are apparent.

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 0% schema description coverage, the description compensates by mentioning 'with a delay,' which implies the delay_ms parameter. It does not explicitly name the parameter or detail its unit, but the default and context make it clear enough for an agent.

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 captures two viewport snapshots and returns a structural diff of changes (actors, camera, selection). The verb 'Capture' and the resource are specific, and the purpose of verifying scene modifications distinguishes it from siblings like ue_viewport_percept or ue_viewport_watch.

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 suggests use for verifying scene modifications, providing a clear context. However, it does not explicitly mention when not to use or compare to alternative sibling tools, so the guidance is good but not exhaustive.

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