ue_viewport_config

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

Annotations already indicate the tool is not readonly, idempotent, and not destructive. The description adds minimal behavioral context beyond listing the configurable attributes; it does not mention side effects, prerequisites, or effects on the system.

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 a single, front-loaded sentence with no unnecessary words. However, it could be more informative without adding length.

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 five optional parameters and no enum constraints, the description fails to explain defaults, parameter interactions, or what the output schema returns. The tool is a configuration operation, yet the description omits critical usage context.

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 description coverage is 0%, so the description must explain parameters. It vaguely lists 'resolution, format, capture rate' but does not map to specific parameters (width, height, format, max_fps, quality) or clarify allowed values, defaults, or constraints.

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 'Configure the viewport perception system (resolution, format, capture rate)' clearly specifies the verb (configure) and resource (viewport perception system), and distinguishes from sibling tools like ue_viewport_percept (perception) and ue_viewport_diff (diff).

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 lacks any guidance on when to use this tool versus alternatives such as ue_viewport_percept or ue_viewport_watch. No explicit conditions or exclusions are provided.

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