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

Goes well beyond the annotations (readOnly, idempotent, closed-world, non-destructive) by disclosing hard limits (200 rows, 300 characters per text/path and across cells, 32 cells max), that href is path-only, that missing ancestry refuses scoped extraction, and that results are untrusted page data. The 'no browser access' clause partly restates openWorldHint=false, which slightly reduces the added value.

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?

Front-loads what is extracted and the result shape, then limits, then failure behavior in a tight sequence of short clauses with no filler. The telegraphic style is dense but every clause carries information.

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?

No output schema exists, and the description compensates by naming the return shape and the per-field constraints, plus limits and error behavior for a read-only extraction tool. The gap is the unexplained task_id and interaction_generation parameters, which matter for correct invocation.

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 carries the full burden, yet it only clarifies 'ref' as an optional observed container scope. task_id and interaction_generation — both required — are never explained, leaving an agent to guess what interaction generation means and why it is mandatory.

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 set: extracting captured list items, table rows and repeated sibling cards, plus the exact output shape {text, href, cells}. An agent can tell this apart from siblings like task_find or task_observe because it operates on already-captured rows rather than finding or observing anew, though the differentiation is implicit rather than naming a sibling.

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?

Gives a clear usage condition and fallback: scoping to an observed container ref is optional, and missing ancestry causes scoped extraction to be refused, in which case a DOM full-page observation should be requested. It does not explicitly say when to prefer this over task_find or task_observe, but the failure routing is concrete.

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