browser_find

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

Describes search behavior (case-insensitive substring for text, case-sensitive regex with flags), and output format (matches with surrounding context under path). Annotations already indicate read-only and non-destructive, and description reinforces these without contradiction.

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?

Relatively concise single sentence that front-loads the action. Some redundancy could be trimmed, but overall well-structured.

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?

Explains return format sufficiently given no output schema. All key behavioral aspects are covered. Annotations handle safety. Minor gap: no explanation of 'accessibility snapshot' or 'ref'.

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 100%, baseline 3. Description adds clarifying details about case sensitivity and regex flag syntax, enhancing understanding 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?

Clearly states it searches the accessibility snapshot for text or regex, returning matching nodes with context. Uses specific verb and resource, and distinguishes itself from full snapshot capture by noting cost savings.

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?

Explicitly advises use when only needing to locate an element and its ref, being cheaper than full snapshot. Does not explicitly mention when not to use, but context is clear.

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