browser_get_by_test_id

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

With no annotations and no behavioral details, the description is a bare statement of intent. It does not disclose what happens if no element is found, whether it returns a handle or locator, or whether it waits for the element. The phrase adds no insight beyond the tool's name.

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 phrase with no superfluous words. It is front-loaded and immediately communicates the core purpose, making it highly concise and structurally 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?

The tool is simple but has no annotations or output schema, yet the description does not explain return values, error behavior, or the context of element lookup (e.g., current page or frame). This leaves significant gaps for an AI agent attempting to use the tool 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 schema has one required parameter 'testId' with no type description, and schema description coverage is 0%. The description only repeats that the element is found 'by test ID', adding minimal meaning about what the parameter represents. It does not explain the format, attribute, or matching behavior expected for testId.

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 '通过测试ID查找元素' (Find element by test ID) clearly states a specific action (find) on a specific resource (element) using a specific locator strategy (test ID). This distinguishes it from sibling get_by_* tools like get_by_role or get_by_text, which use different locators.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparative context to sibling locator tools, leaving the agent to infer usage from the tool name alone.

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