browser_extract_tables

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

With no annotations, the description must fully disclose behavior. However, it only states 'visible tables' without explaining how visibility is determined, whether scrolling occurs, or any limitations. No mention of side effects, performance, or required permissions.

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?

Extremely concise at 10 words, front-loaded with action and object. However, it sacrifices necessary detail, making it barely adequate for a tool with two undocumented parameters.

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 simplicity of the tool (2 optional params, no output schema), the description is incomplete. Missing information includes what the return data looks like, whether the extraction is synchronous, and any prerequisites (e.g., page must be loaded).

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 description provides no explanation for the two parameters ('max_rows', 'max_tables'). Since schema coverage is 0% (no descriptions in input schema), the description completely fails to add meaning beyond the parameter names and defaults.

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 'visible tables from the current browser page', and adds context 'after navigation/interactions'. This distinguishes it from siblings like 'web_extract_tables' which might operate on web pages in a different context, making purpose specific and clear.

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?

No guidance on when to use this tool versus alternatives such as 'web_extract_tables' or other extraction tools. The description only mentions 'after navigation/interactions' as a condition but does not provide when-not-to-use or alternative tools.

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