browser_extract

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context beyond listing extractable data types; it does not disclose limitations, preconditions, or response format. No contradiction with annotations.

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 concise sentence, front-loaded with the core action and immediately enumerating the extractable types. 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?

For a simple tool with one parameter and no output schema, the description conveys the general purpose but omits critical details like the fact that it operates on the current page (implied but not stated) and the exact accepted values for 'mode'. An agent might need to infer how to use it correctly, so completeness is adequate but not strong.

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% (no description for 'mode'), so the description must compensate. It lists potential values ('text, elements, links, tables or main') which hints at valid modes, but does not explicitly map them to the parameter or clarify defaults. This adds some meaning beyond the schema but not complete clarity.

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 a clear action ('Pull structured page data from the DOM') and specifies the resource (DOM) and the types of data (text, elements, links, tables, main). This is specific and reasonably distinct from sibling tools like browser_observe, though it does not explicitly name a sibling or differentiate.

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 guidance on when to use this tool versus alternatives such as browser_observe or browser_search. It does not mention conditions, exclusions, or situations where a sibling would be preferred.

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