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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that — it is a private, persistent live stream, requires waiting for a loading state, and supports on-demand screenshots of the current view. It does not cover auth, lifetime, or rate limits, but the added context is substantial.

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?

One compact sentence that front-loads what the resource is and follows with the usage rule. The phrasing ('a live view through your eyes, for a browser tool') is slightly convoluted but nothing is wasted.

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?

With no output schema, the description does explain what comes back (a private link) and how to consume it, and the readOnly annotation covers safety. For a zero-parameter tool this is close to complete, though it never clarifies when this is preferable to sibling inspection tools.

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, which sets the baseline at 4. Schema coverage is 100% and there is nothing for the description to compensate for on the parameter side.

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 conveys that this yields a private live-view link tied to the agent's viewpoint, but it never states a clean verb+resource ('returns a URL to a live camera feed') and does not distinguish it from siblings like 'look' or 'face'. The purpose is inferable but left vague.

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?

It gives post-return consumption instructions (open once, wait for 'Loading...' to clear, keep it open, screenshot on demand) but offers no guidance on when to call this tool versus the many world-inspection siblings. No conditions or alternatives are named.

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