browser_read_table

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

With no annotations, the description carries the behavioral burden alone: it does disclose the 200-row cap, which is genuinely useful. It does not say whether results are truncated/paginated, whether the read is read-only against page state, or what happens if the table has more rows.

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?

One sentence, front-loaded with the cap, no filler. Nothing is wasted; the gaps are omissions rather than verbosity.

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?

A single undocumented parameter, no annotations, and no output schema leaves key questions open: how ref is obtained and what the returned rows look like. For a data-extraction tool the description should at least tie ref back to the snapshot.

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 description coverage is 0%, so the description must explain the required 'ref' parameter — yet it never mentions it. An agent is left guessing whether ref is a table index, CSS selector, or a snapshot node reference.

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?

States a specific verb and resource ('Read ... from a table') plus scope ('in the current snapshot') and a row cap. It is distinguishable from browser_snapshot, which presumably captures the whole page, though the relationship is never made explicit.

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 indication of when to prefer this over browser_snapshot, browser_find, or browser_inspect_element, and no prerequisites (e.g. that a snapshot must exist first). Usage is only inferable from the tool name.

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