browser_assert

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description correctly adds value by emphasizing 'deterministic' checks and 'Returns pass/fail'. The enumerated check types materially expand behavioral transparency because the schema otherwise reveals only an opaque array of additionalProperties-objects. No contradiction with 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 two-sentence intro is front-loaded with purpose and outcome, and the example block is compact and information-dense. Each line illustrates a distinct check type with no filler or redundant words.

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 description is complete enough for a tool with a polymorphic checks parameter and an output schema. It covers all major assertion categories and return behavior. Minor gaps remain around exact pattern-matching semantics and the precise pass/fail output structure, but those are not critical for selecting and invoking the 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 description coverage is 0%, and the checks items are 'additionalProperties: true', giving no semantics. The description fully compensates by presenting 11 concrete check object shapes with field names like pattern, text, ref, role, name, min, and expr. The session parameter is adequately covered by its schema default.

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 ('verify') and names the resource ('current page'), and explicitly states the return contract ('Returns pass/fail'). The extensive list of concrete check types makes it unmistakable what the tool does and differentiates it from siblings like browser_observe or browser_act.

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 clearly implies this tool is for deterministic assertions on the current page, and the check examples show common scenarios. However, it never explicitly states when to prefer this over siblings such as browser_observe, browser_act, or browser_goal, nor does it mention cases where it should not be used.

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