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

Goes well beyond the annotations by disclosing the single-use nature of the link, the ttl open-window (default 60, capped at 300), the 30-minute session ceiling, and the one-viewer-per-account concurrency constraint. These are non-obvious operational traits the agent would otherwise have to discover, and nothing contradicts the readOnly=false/openWorld=true annotations.

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?

Front-loads the core deliverable (single-use live-view link) and its constraints, then appends quality/compression and the endpoint. Dense but nearly every clause carries load; the trailing raw endpoint is the one element that adds little for an agent choosing a tool.

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 correctly explains what the tool returns (a shareable link) plus its TTL and session lifetime, and it covers the concurrency limit. It omits required permissions/authorization context, which is a minor gap for an open-world mutation-style 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?

Schema coverage is 100%, so the baseline is 3; the description adds genuinely new meaning by framing quality/compression as the 'starting picture quality, changeable in the viewer' and clarifying that ttl is the deadline to open the link, not the session length. It does repeat the 0-9 ranges and defaults already present in the schema, capping the score below 5.

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 concrete verb+resource (opens a live view of the agent's browser via a single-use link) and explains the two modes, so the agent knows exactly what the tool produces. It does not, however, name or contrast sibling tools such as muse_get_browser, muse_release_browser, or muse_revoke_browser_viewers, leaving differentiation to inference.

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?

Usage is implied through the mode descriptions (view to watch, control to watch and take over with mouse/keyboard), which tells the agent the intended audience and task. But there is no explicit when-to-use/when-not or routing to alternative tools, so the guidance is suggestive rather than directive.

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