frame_selection

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

Given no annotations, the description adds valuable behavioral context: NO_UNDO (irreversible viewport change), only adjusts view (not a capture), and response passes through `apply_response_cap`. These traits go beyond what the schema or annotations would convey, though the exact meaning of `apply_response_cap` remains vague.

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 very short, front-loaded with the core method name and the key 'only adjusts view' statement. No filler, but the Chinese-English mix and technical jargon may reduce clarity for non-Houdini users.

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, no output schema, and an unexplained parameter, the description is incomplete. It highlights no-undo and non-screenshot behavior but omits the meaning of `ctx` and does not cover expected usage scenarios, which is a significant gap even for a simple tool.

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 only parameter `ctx` has zero schema coverage and the description does not explain what it is or how to construct it. With 0% coverage, the description needed to compensate but fails entirely.

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?

Description names the underlying method (`viewport.frameSelected()`) and explicitly states it 'only adjusts the view' and does not screenshot, making the core purpose reasonably clear for users familiar with Houdini. It distinguishes from screenshot tools like `capture_pane_screenshot`, though it could more explicitly say it frames the current selection.

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?

Provides a negative usage hint ('not screenshot') but no explicit guidance on when to use this tool vs alternatives like `frame_all` or `set_viewport_camera`. No when-to-use/when-not-to-use scenarios are described.

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