live_browser_preview

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

No annotations are provided, so the description carries full responsibility but only gives minimal info. It doesn't explain what 'preview' means, side effects, or how the stop flag behaves. The behavior regarding stale IDs vs. URIs vs. paths is only hinted in the schema, not in the description.

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 extremely concise at one sentence, which is good for front-loading. However, it may be too brief given the tool's complexity, sacrificing completeness for brevity.

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?

Given the tool has a nested object parameter, a boolean flag, and many sibling tools with similar purposes, the description is far from complete. It lacks information on return values, error handling, prerequisites (e.g., from live_browser_search), and how preview relates to other operations.

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 description does not mention parameters at all, and schema description coverage is 0%. While the schema has detailed descriptions for item properties and stop, the description fails to guide the agent on how to use these parameters effectively.

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 clearly states the tool is for previewing or stopping preview of a BrowserItem. It specifies the verb ('Preview' or 'stop previewing') and resource ('BrowserItem'), making the core action clear. However, it does not differentiate from siblings like live_browser_load or live_browser_search, which could be related.

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. For example, it doesn't say whether previewing is distinct from loading, or if this tool is meant for temporary previews. There are no exclusions or context hints.

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