browser_get_by_title

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states 'find element by title attribute' and does not mention whether it returns a locator, waits for the element, handles multiple matches, or errors if not found. No behavioral details are disclosed.

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 short sentence, but it largely restates the tool name ('find element by title attribute'), adding little value. It is under-specified rather than appropriately concise, and the brevity wastes the opportunity to provide needed context.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns, how exact matching works, or any error/edge-case behavior. A single-phrase description is insufficient for a selectable element lookup 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%, so the description should compensate. It hints that 'text' refers to the title value, but the 'exact' boolean parameter is not explained at all. The parameter semantics are only partially clarified.

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 '元素' (element) via the 'title' attribute, which distinguishes it from sibling get-by-* tools (e.g., get_by_text, get_by_label). Even though it's brief, the purpose is unambiguous and specific to the title attribute.

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?

There is no guidance on when to use this tool versus alternatives like browser_get_by_text or browser_get_by_label. The only implied usage is 'by title attribute', but no exclusions or context are provided.

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