browser_observe

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the action and result but does not disclose whether it is read-only, what happens if no page is loaded, or any side effects. The implicit 'observe' suggests non-destructive, but this is not explicit. The description lacks transparency about behavior.

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, efficient sentence with no unnecessary words. It front-loads the action and resource. However, it is too brief, bordering on under-specification, but structurally it is concise and not verbose.

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's simplicity (one optional parameter, no annotations, no output schema), the description should provide enough information for correct invocation. It does not explain what 'observed controls' means, does not describe the output format, and does not clarify the max_elements parameter. It is incomplete for an agent to use effectively.

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 input schema has one parameter (max_elements) with 0% schema description coverage. The description does not mention this parameter at all, so the agent cannot infer its purpose or how to use it. The description fails to compensate for the missing schema documentation, leaving the parameter's meaning entirely ambiguous.

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 a specific action ('List') and a resource ('observed controls and the visible text of the current page'). It distinguishes itself from siblings like browser_search and browser_extract by specifying what it returns, though it does not explicitly name alternatives. This meets the 'clear but no sibling differentiation' criterion.

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 provides no guidance on when to use this tool versus alternatives like browser_extract or browser_search. It does not mention contexts where this tool is preferred, nor does it state exclusions or prerequisites. No usage context is given.

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