wave_view_file

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

With no annotations provided, the description carries the full behavioral burden. It discloses that a preview block is opened and that a helper block is required, but does not explain side effects, whether existing blocks are replaced, permission requirements, or what happens if the helper is missing.

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?

Two short sentences with no wasted text. The main purpose is front-loaded, and the prerequisite follows immediately.

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 simple two-parameter UI action with full schema coverage and no output schema, the description is mostly complete. It covers purpose and the Seashell Helper prerequisite, though it could say more about side effects and failure mode.

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 100%, so both tab_id and file are already documented in the input schema. The description adds no additional parameter meaning beyond that, which is acceptable given full schema coverage.

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 and resource: opening a file in a Wave Terminal preview block. That clearly distinguishes it from filesystem reads or editing, though it does not explicitly contrast with sibling tools such as wave_edit_file.

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 gives a key prerequisite: the Seashell Helper block must be available. It implies previewing a file rather than editing it, but does not explicitly say when to choose this over wave_edit_file or other preview-related tools.

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