find

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

No annotations provided, so description must convey behavior. It mentions optional action but not what actions are possible (though schema shows enum). Does not explain search scope, timeout, return value, or side effects. Severe lack of behavioral context.

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?

Single sentence is concise but too minimal for a tool with 30 parameters. Could benefit from structured list or additional sentences to improve scannability.

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 complex tool with 30 parameters and no output schema or annotations, the description is grossly incomplete. It does not explain return value (element info?), error states, or how to chain actions. Leaves the agent guessing.

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 70%, so many parameters have inline descriptions. However, the tool description adds no overarching semantics or patterns for using the 30 parameters. It fails to link parameters like locator, query, action together meaningfully.

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 the tool finds an element and optionally acts on it. It distinguishes from sibling tools that purely act (e.g., click, fill) by combining find+act. However, it could be more specific about what 'element' means (UI element, etc.).

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?

No guidance on when to use this tool versus alternatives like separate find-then-act sequences. For a tool that combines find and act, it should clarify tradeoffs with using dedicated find (get, snapshot) and action tools.

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