navvi_find

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

Discloses automatic browser chrome offset correction, which is a key behavioral trait. With no annotations provided, this adds value, though it could mention error handling or timeout behavior for completeness.

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?

Well-structured with clear sections: purpose, primary usage indicator, workflow, and special case. Some redundancy in emphasizing its primary role, but overall efficient.

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?

Covers primary use case, workflow, and dropdown handling. Given the presence of an output schema (implied) and the tool's moderate complexity, the description provides sufficient context for an agent to use it correctly.

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 explains the 'selector' parameter contextually and hints at 'all' through the dropdown example, but the 'persona' parameter is unmentioned. With 0% schema description coverage, the description partially compensates but leaves a gap.

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 finds elements by CSS selector and returns screen-ready coordinates, explicitly distinguishing it from sibling tools like navvi_click and navvi_fill by positioning it as the primary coordinate getter.

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?

Provides explicit workflow instructions (navvi_find -> coordinates -> navvi_click/navvi_fill -> navvi_screenshot) and specific guidance for dropdowns, including alternative selector strategies and use of the 'all' parameter.

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