browser_observe

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the concrete behavior of listing controls and visible text, but does not disclose details like pagination, element limits, or how 'observed controls' are determined. It does not contradict the 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?

The description is a single front-loaded sentence with no filler. Every word contributes to the core meaning, and it is appropriately concise for a simple observation 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?

For a simple tool, the description gives a basic idea of what it returns, but it omits any explanation of the sole parameter max_elements and does not clarify the meaning of 'observed controls'. With no output schema, the description should carry more of the semantic load than it does.

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%, and the description does not mention max_elements at all, so the description does not compensate for the missing schema documentation. The parameter name and type give an indirect clue about its limiting behavior, but the agent gets no explicit semantics or guidance on when to provide it.

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 uses a specific verb ('List') and a clear resource ('observed controls and visible text of the current page'), which distinguishes this read-only inspection tool from siblings like browser_click, browser_type, and browser_screenshot. Even without explicitly naming alternatives, the action and scope are unambiguous.

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 description implies the tool is for inspecting the current page's controls and text, which is a sensible use case, but it gives no explicit guidance about when to prefer it over siblings like browser_extract, browser_search, or browser_screenshot. No exclusions or alternative conditions are stated.

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