chrome_extract

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

No annotations are provided, so the description carries full burden. It discloses that output is JSON or error message but fails to clarify precedence when both selector and javascript_expression are provided, or behavior when neither is specified. Side effects are not addressed.

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 concise with a clear purpose statement, an args list, and return info. It is front-loaded with the main action. Minor formatting (bullet-like lines) but no wasted words.

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 0% schema coverage and no annotations, the description should cover parameter interactions and error scenarios. It explains basic usage but lacks details on mutual exclusivity of selector and javascript_expression, and does not describe potential failure modes or output schema content.

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 coverage is 0%, so description must compensate. It explains each parameter (session_id, selector, attribute, javascript_expression) briefly, adding meaning beyond empty defaults. However, it does not clarify mutual exclusivity or dependency requirements, leaving ambiguity.

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 explicitly states 'Extract data from a page by selector or by JavaScript expression,' clearly specifying the verb (extract) and resource (data from a page). It distinguishes the two methods, avoiding tautology and providing specific purpose.

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 implies usage for extracting data but provides no explicit guidance on when to use this tool versus siblings like chrome_click or chrome_screenshot. No exclusions or alternative tools are mentioned.

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