bridge_render_view

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuine trait beyond the schema: rendering happens via IScreenshotService without synthesizing mouse/keyboard/Computer Use input, which signals a non-interactive, low-side-effect operation. It omits whether an output file is overwritten, what format is produced, and any preconditions or error behavior.

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 single sentence is front-loaded with the action and free of filler, and the 'no mouse/keyboard/Computer Use' qualifier is compact. It is appropriately sized, though the extreme terseness leaves substantial gaps that a slightly longer definition should have filled.

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 five-parameter tool with no annotations, no output schema, and 0% schema coverage, the description is far too thin. It explains the rendering mechanism but says nothing about required inputs, where the rendered artifact goes, or the operational context needed to call it correctly.

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% across five parameters (project, output, width, height, entity_id), and the description supplies no meaning for any of them. With low coverage the description must compensate, and it does not mention a single parameter.

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 gives a clear verb+resource ('Render a native view') and identifies the underlying mechanism (IScreenshotService), which distinguishes it from UI-driven automation approaches. It stops short of explaining what a 'native view' is relative to sibling tools like bridge_export_pdf or bridge_preview_on_copy, so it is clear but not fully differentiated.

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 clause 'no mouse, keyboard or Computer Use calls' implies this is the headless, non-interactive way to obtain a rendered view, which is useful implied guidance. However, it never states explicit when-to-use versus alternatives, nor any prerequisites (e.g., project must be open, entity_id selection rules).

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