browser_cursor_style

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

No annotations are provided, so the description carries the full burden. It discloses the privacy-mask effect (blurring contacts and numbers during recording or screen sharing), which is genuinely useful, but says nothing about defaults, persistence of state across calls, or what happens to unspecified toggles.

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?

A single front-loaded sentence enumerating the four capabilities with no filler. It is efficient, though the enumeration is dense and would benefit from a short lead clause about the recording context.

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?

Five optional parameters, no annotations, and no output schema mean the description must carry the behavioral load. It covers the visible effects but omits the teachButton toggle, default behavior when no arguments are passed, and whether settings persist between calls.

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 60%, and the description names four of the five toggles, adding context for the HUD and privacy mask beyond the schema labels. However, teachButton is absent from the description, and no default or omission semantics are given for any 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?

States a specific verb pair (muestra/oculta) and enumerates the resources affected: visual cursor, trail, live token HUD, and privacy mask. An agent can distinguish this from siblings like browser_cursor or browser_record_start, though the overlap with browser_cursor is not explicitly resolved.

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 phrase 'al grabar o compartir pantalla' hints at the recording/screen-sharing context, but there is no explicit when-to-use guidance, no statement about calling it with zero arguments, and no disambiguation from browser_cursor or browser_teach_start.

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