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 of behavioral disclosure, but it only says 'Get' and names a single argument. It does not reveal return format, side effects, error behavior, or what a null pane_name means, so the agent has little to rely on beyond the verb.

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 compact and front-loaded with the purpose, followed by a short argument note. There is no filler or redundancy, though it is borderline under-specified rather than elegantly concise.

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?

For a tool with no annotations and no output schema, this description is too sparse. An agent cannot determine what viewport settings are returned, whether omitting pane_name is valid, or how this relates to the many viewport-related sibling tools, making correct invocation uncertain.

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. The line 'pane_name: Pane tab name' adds only a small clarification over the schema title 'Pane Name' and does not explain valid values, optionality semantics, or how to target a specific pane tab.

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 resource ('viewport settings for a pane tab'), so an agent can infer the core operation. However, it does not enumerate which settings are returned or distinguish it from viewport-related siblings such as list_panes, get_scene_info, or set_viewport_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?

No guidance is provided on when to use this tool versus alternatives. There are no explicit contexts, exclusions, preconditions, or references to sibling tools like set_viewport_camera or list_panes, leaving usage entirely implied.

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