get_viewport_info

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

With no annotations, the description carries the full burden. It clearly indicates a read operation via 'Get' and lists the returned data, but it does not explicitly state that the tool has no side effects or does not modify the scene. While implied, it is not disclosed explicitly, which is a minor gap given the absence of annotations.

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, tightly written sentence that front-loads the purpose ('Get current viewport state') and then lists the specific elements returned. Every word earns its place, with no filler or redundancy.

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?

The description lists the key data returned (active camera, shading mode, view matrix, cursor position), which is sufficient for a simple getter with no output schema. It does not mention return format or whether it is a snapshot vs. live reference, but these are minor and not critical for a tool of this simplicity.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly omits parameter details since there are none to document. The description adds no parameter semantics because none are needed, satisfying the baseline.

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 states a clear verb ('Get') and a specific resource ('current viewport state'), then enumerates exactly what is returned: active camera, shading mode, view matrix, and cursor position. This fully distinguishes it from sibling tools like set_viewport_shading or get_viewport_screenshot, which either modify state or capture images.

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 clearly implies this is a read-only query for current viewport state, and its purpose is obvious given the sibling set (setters and screenshot tools). However, it does not explicitly name alternatives or state when not to use it, though the context makes the intended usage self-evident.

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