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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds 'revision-aware,' which hints at concurrency control via expectedRevision, but doesn't explain the mechanism or consequences. It provides some extra context beyond annotations but remains vague about side effects and failure 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 sentence with no filler. Key elements—scope ('one'), routing modes, and revision awareness—are packed in. It is economical and front-loaded, though the jargon ('revision-aware', 'human browser action') may reduce clarity slightly. It earns its place but could be more accessible.

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 complexity (8 parameters, nested target object, no output schema) and low schema coverage, the description is far from complete. It doesn't mention that action must come from browser_capabilities, how to specify the target, retry semantics, or the expectedRevision contract. An agent would struggle to invoke this tool correctly based on the description alone.

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 low (25%), so the description must compensate for undocumented parameters like params, target, retries, timeoutMs, retryDelayMs, and expectedRevision. It does not describe any of these; the only implicit hint is 'DOM, browser-input, or native routing' for the engine parameter. This fails to help the agent understand how to construct valid invocations.

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 states a specific verb ('execute') and resource ('human browser action'), and the word 'one' distinguishes it from browser_batch. It also mentions routing through DOM, browser-input, or native, which clarifies its scope. However, it doesn't explicitly name siblings or state that action names come from browser_capabilities, so it's clear but not maximally differentiating.

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?

There is no guidance on when to use this tool versus alternatives (e.g., browser_batch for multiple actions, browser_query for reading state). It doesn't mention prerequisites like calling browser_capabilities first or supplying expectedRevision. The description simply states what it does, leaving the agent to infer usage context entirely.

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

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to repeat those. It adds the default stop-on-failure behavior, which is not in the annotations, and implies ordered execution. However, it does not disclose other traits like side effects on the browser state or that the sequence may be interrupted. The added context is modest, earning a middle score.

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 that front-loads the core purpose and a key default behavior. It contains no wasted words and is appropriately brief for a tool whose schema carries the heavy detail. Every clause earns its place.

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?

This is a complex batch tool (up to 100 actions, many subfields) with no output schema, yet the description is minimal. It does not explain when to prefer it over sibling tools, how actions relate to browser_capabilities, or what the stopOnError parameter controls in practice. While the schema provides technical detail, the description fails to provide the usage context an agent needs to decide when to invoke this tool, leaving significant gaps.

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% – the description provides no information about the two parameters (actions, stopOnError) or their meaning. The schema itself does contain detailed sub-field descriptions, but the description does not compensate for the low coverage. An agent would have to rely entirely on the schema, and the description adds no semantic help for choosing or structuring the parameters.

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 states a specific action ('execute an ordered sequence') and a clear resource (one selected browser), with a notable behavioral detail (stopping on failure by default). It clearly distinguishes from the sibling browser_action which likely runs a single action, though it does not name that sibling explicitly. This is clear but not maximally explicit about alternative tools.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies use for multiple actions but does not state 'use this instead of browser_action for sequences' or provide exclusions. The 'stopping on failure' default is a behavior, not a usage condition. An agent must infer from the name and schema that this is for batching.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior on which the description builds. The description adds useful context about default output (action names, categories, compact runtime state) and how passing filters changes the response, which goes beyond the annotations without contradicting them.

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 two sentences with no filler. It front-loads the core purpose, then gives clear, compact usage rules. Every clause earns its place and no information is redundant with the schema or annotations.

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 low complexity, fully optional parameters, rich annotations, and an output schema, the description is complete enough for an agent to call it correctly. It explains the default behavior, the effect of filters, and when to request full detail, leaving no critical gaps.

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%, so the description must carry the parameter semantics. It explains the roles of 'actions' and 'categories' for focused metadata and 'detail' for full reference retrieval. While it does not exhaustively describe every parameter, it provides meaningful guidance that maps directly to the schema fields.

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 states a specific verb and resource: 'List browser relay actions and runtime availability.' This clearly identifies the tool as a metadata/listing operation and distinguishes it from siblings like browser_action or browser_snapshot, though the term 'browser relay actions' is somewhat jargon-heavy and the distinction is implied rather than explicit.

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 actionable usage guidance: pass only intended action names or categories for focused metadata, and request full detail only when the entire reference is needed. It does not explicitly compare against sibling tools or state exclusions, but the parameter-level guidance is clear and practical.

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

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

Annotations already indicate destructive, non-read-only behavior. The description adds a useful per-chunk integrity-check detail and a source precondition, but does not clarify overwrite behavior, failure cases, or what happens if the source file is not available. This is acceptable but not rich.

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 sentence with the operation and destination front-loaded illusion, and the integrity-check detail appended without filler. Every part earns its place.

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?

The direction and purpose are clear, and the tool is simple with only three parameters. However, overwrite semantics, destination handling, and return/result behavior are not described, leaving moderate gaps for an agent calling it autonomously.

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 provides no meaning for remotePath, destinationPath, or overwrite. The agent must infer path semantics and overwrite behavior purely from parameter names and the schema.

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 names a specific verb and resource: 'Copy ... browser-device file' to the MCP client machine. It also scopes the source as a completed download or explicitly supplied file, distinguishing it from sibling tools like browser_upload_files.

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 gives clear context for when to use the tool: to retrieve a completed download or other explicitly supplied device file to the client machine. It does not explicitly name alternatives or state when not to use it, stopping short of a 5.

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

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 event categories and the notion of 'recent' events, which is useful context. It doesn't disclose pagination behavior, ordering guarantees, or what happens when no events exist, but the annotations carry the main behavioral burden.

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 sentence that front-loads the verb and resource, then lists the event categories. It is concise and every word earns its place, though it could be slightly more structured with a second sentence for usage guidance.

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 read-only, idempotent tool with no required parameters and no output schema, the description is mostly adequate. The main gap is that it doesn't explain the afterSequence parameter or describe the return format, but the annotations cover the safety profile and the event list gives a good sense of what will be returned.

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%, so the description must compensate for the two parameters. The description mentions 'recent' events, which hints at the limit parameter, but it doesn't explain afterSequence at all. The parameter names are fairly self-explanatory, but the description adds minimal semantic value beyond the schema.

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 states a clear verb ('Read') and resource ('browser events'), and enumerates the event categories (relay, navigation, DOM revision, request, download, error, lifecycle). This distinguishes it from sibling tools like browser_snapshot or browser_action, though it doesn't explicitly name a sibling alternative.

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 this is for reading event history rather than taking actions or capturing snapshots, which helps an agent choose it over browser_action or browser_snapshot. However, it doesn't explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites.

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

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

The description adds important context beyond the annotations by warning that some observations 'may activate a tab or attach debugger instrumentation.' This qualifies the 'read query' label and introduces realistic side effects, which is especially valuable given that readOnlyHint is false. The description does not contradict the annotations; it complements them.

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 two sentences with no wasted words. The primary purpose is stated first, followed by a concise caveat. Every word contributes to comprehension, and the length is appropriate for the tool's generic dispatching nature.

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?

Even though the schema describes the 'action' parameter as returned by browser_capabilities, the description omits crucial context: how to discover valid actions, what the output format is, how 'params' should be structured per action, and what side effects may be expected beyond the vague note. The tool is complex with nested targets and retry options, and no output schema exists, so the description is insufficient for an agent to invoke it effectively on its own.

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 itself explains none of the eight parameters, despite schema description coverage being only 25%. It does not compensate for gaps around 'action,' 'engine,' 'target,' or retry fields一波. The only parameter explanation comes from the schema itself (for 'action' and 'engine'), so the description adds no value to parameter understanding.

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 states a specific action: 'Run a catalog-defined read query.' This clearly identifies the tool's purpose as executing predefined read operations and differentiates it from mutation or snapshot tools by emphasizing the read nature. However, it does not explicitly name a sibling tool or further clarify what distinguishes a 'query' from browser_capabilities or browser_action.

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_action or browser_batch. It never mentions any condition that would select this tool over others, nor does it explain prerequisites such as calling browser_capabilities first to obtain valid actions. The 'catalog-defined' phrase hints at external definitions but leaves the decision entirely to inference.

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

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

The description adds meaningful behavioral context beyond the annotations: it explicitly states the tool does not change the DOM (non-destructive), and it explains default semantics for omitted properties: 'Omitted visible/enabled mean true; omitted editable/readonly mean false.' This is valuable because the schema has no descriptions for these boolean fields. The annotations already indicate idempotentHint=true and destructiveHint=false, but the description reinforces and adds the default-value semantics, which is beyond what annotations provide.

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 three sentences, each earning its place: the first states the core function and non-mutation guarantee, the second clarifies default boolean semantics, and the third routes coordinate needs to another tool. It is front-loaded with the most important information and has no filler.

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 5 parameters, no output schema, and 0% schema description coverage, the description does a good job of covering the key behavioral aspects: non-mutation, bounded/sparse output, and default boolean semantics. It could be more complete by explaining what 'revisioned' means and how the element catalog relates to other browser tools, but for an observation tool with idempotentHint=true, it covers the essential context an agent needs.

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%, so the description must compensate. It does partially: it explains the meaning of omitted boolean parameters (visible/enabled/editable/readonly) and mentions 'bounded' and 'sparse' which relate to maxElements. However, it doesn't explain tabId, allFrames, includeHidden, or includeScreenshot in detail. The description adds some semantic value but leaves several parameters to be inferred from their names.

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's purpose: 'Return bounded page state and a sparse, revisioned element catalog without changing the website DOM.' This is a specific verb ('return') and resource ('page state' and 'element catalog'), and it explicitly distinguishes itself from mutation tools by noting it does not change the DOM. It also differentiates from coordinate-related tools by pointing to getBoundingBox.

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 clear context for when to use this tool: when you need page state and an element catalog without DOM changes. It also gives a specific exclusion: 'Use getBoundingBox when coordinates are needed.' However, it doesn't explicitly name sibling alternatives like browser_query or browser_action, nor does it state when not to use it in favor of those. The guidance is clear but not exhaustive.

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

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

Annotations already state destructiveHint=true and readOnlyHint=false. The description adds that this tool transfers files and sets the input, which is a useful behavioral outcome. It does not disclose potential side effects like overwriting existing state or triggering change events, but the annotations cover the main safety traits.

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, tightly-worded sentence with zero filler. The action is front-loaded and every word adds meaning.

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?

The nested target object is complex, yet the description offers no guidance on how to specify the target (e.g., by coordinates, locator, or elementId), nor does it mention timeoutMs or return behavior. There is no output schema and the description leaves too much to inference for a tool with this many target options.

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?

With 0% schema description coverage, the description partially compensates by indicating that 'paths' corresponds to files or directory contents and 'target' identifies the file input. However, it does not explain how to choose among the numerous target sub-fields (coordinates, locator, elementId) or what timeoutMs does.

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 ('Transfer') and resource ('files or directory contents') and clearly states the subsequent action ('set the targeted file input'). This distinguishes it from the sibling browser_download_file and other browser tools.

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 usage context: it is the tool to use when files need to be placed into a browser device and a file input must be set. The mention of 'selected browser device' and 'targeted file input' gives clear context, though no explicit alternative tools are named.

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