browser_extract_content

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 mentions 'smart content detection' but does not explain how it works, what happens with dynamic or complex pages, or whether it waits for rendering. It also does not indicate what the output structure looks like or any failure modes.

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 that effectively communicates the tool's core purpose without unnecessary words. It is front-loaded with the action and resource, and every word adds value.

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's moderate complexity (4 parameters, no output schema, no annotations), this one-sentence description is insufficient. It does not explain the return format, how modes affect output, or what 'clean markdown' means in practice, leaving significant gaps for an agent trying to use it effectively.

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 input schema has 100% coverage with descriptions for all four parameters, so the baseline is 3. The tool description itself adds no additional parameter-level meaning beyond the schema. The description does not elaborate on mode behavior, selector usage, or pagination semantics further.

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 'Extract', the resource 'page content', and the output format 'clean markdown'. The phrase 'smart content detection' adds a clear sense of scope and helps distinguish this from sibling tools like browser_snapshot or browser_interact, which focus on different actions.

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 explicit guidance on when to use this tool versus alternatives. Sibling tools such as browser_snapshot or browser_interact may serve overlapping purposes, but the description does not mention any exclusions or provide context for selection. The usage is only implied by the description's wording.

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