find

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

With no annotations, the description carries the full behavioral burden, but it only says the tool produces a narrowed snapshot. It does not state that the operation is read-only, whether it has side effects, what the return format looks like, or how matching elements are presented.

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, front-loaded sentence with no wasted wording. Its brevity is appropriate for conciseness, though it contributes to gaps in other dimensions.

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 an 8-parameter tool with no annotations and no output schema, the description is too sparse. It omits most parameter semantics, return shape, tab default behavior, timeout handling, and the relationship to the snapshot sibling.

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 only 38%, so the description should compensate but does not. It mentions text and regex matching behavior but leaves max, tab, boxes, format, selector, and request_timeout unexplained.

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 operation: a snapshot narrowed to elements whose name, text, value, or href matches text or regex. It clearly distinguishes the filtered result from a full snapshot, though the name 'find' is generic and it does not explicitly contrast with the sibling snapshot tool.

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?

Usage is implied: use this when you need only elements matching text or regex rather than a full snapshot. However, it gives no explicit when-to-use/when-not guidance, no alternatives, and no prerequisites.

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