armorpaint_set_viewport

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

Annotations provide no positive hints, so the description carries the burden. It usefully discloses the valid mode values and their meanings, but it does not state whether this is a pure view-state change, whether it affects the project, or whether any prerequisites exist. The mapping adds meaningful context, but side effects remain opaque.

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 that packs the complete mode mapping into a compact list with no filler. Every word is useful and the numeric mapping is easy to parse.

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 zero schema description coverage and five parameters, the description is incomplete. The mode channel mapping is thorough, but the environment and wireframe parameters are unexplained, and no output/behavioral context is provided. An agent could call the tool with mode but would lack guidance for other intended settings.

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 compensate. It thoroughly explains the 'mode' parameter's channel mapping, which is valuable. However, four of five parameters (wireframe, environment, environment_angle, environment_strength) receive no semantic explanation beyond their schema types and names.

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?

States a specific verb 'Set' and resource 'viewport channel', and enumerates the exact channel-mode mapping. This clearly distinguishes it from related viewport tools like capture_viewport or set_camera, at least by action and scope.

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?

Usage is implied: use it when the user wants to change the viewport display channel. However, there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools like capture_viewport.

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