find_by_label

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

No annotations are present, so the description bears full burden of disclosing behavior. It only states the action without mentioning error handling, return value, side effects (like scrolling or waiting), or whether the element must be visible/interactive. This omission leaves the agent uncertain about runtime behavior.

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 sentence, which is concise but overly minimal. It provides no structure such as examples, notes, or additional context. While brevity is valued, the description sacrifices necessary information for conciseness.

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?

Despite having an output schema, the description fails to provide enough context for a simple one-parameter tool. It omits what the tool returns (e.g., element handle, coordinates, or null), how it behaves if not found, and relationship to sibling tools. The description is incomplete for an agent to reliably use 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%, yet the description adds no detail about the 'label' parameter. It does not clarify whether the label refers to the HTML label element's text, the 'aria-label' attribute, or the 'for' attribute. The agent lacks semantic understanding beyond the parameter name and type.

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 verb 'Find' and the resource 'form element' with the criterion 'by label'. It distinguishes from siblings like find_by_placeholder or find_by_role by specifying the selector type, though it could be more precise about what constitutes a 'label'.

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 is provided on when to use this tool versus alternatives such as find_by_role, find_by_text, or fill_by_label. The description lacks any context about prerequisites, limitations, or typical use cases.

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