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

The description explains the side effect that justifies readOnlyHint=false: the table is saved to the user's Puley history, and reads consume account limits. That is exactly the extra context annotations can't convey. It stops short of disclosing failure behavior or cost scaling with the pages parameter.

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?

A single front-loaded sentence that leads with the output and follows with constraints; no filler. It is slightly run-on with the parenthetical example list interrupting the flow, 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?

For an open-world scraping tool with no output schema, the description should say at least what comes back (a table reference? rows inline? a link to history?) and roughly how much data the pages setting can pull. It covers cost and persistence but leaves the return shape and page-limit semantics undefined.

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 carry the load. It does well for fields by giving a concrete example array, and link is implied by "a page," but the pages parameter (default 3) is never explained — only a vague reference to "the page's own pagination" appears, leaving the agent unsure whether pages caps crawling or overrides site pagination.

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?

"Every product, job or listing on a page, with the fields asked for" plus "turn a page into a table" states the operation (extract structured rows from one page) with concrete examples of the fields. It is clear what the tool produces, but it never names how it differs from close siblings like read, read_site, see_page, or search_marketplace, so differentiation is left to inference.

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 describes only what the tool does, never when to pick it over the many alternatives listed (read, see_page, read_site, search_marketplace, more_results). "following the page's own pagination" hints at a use case for multi-page listings but gives no explicit when/when-not rule or alternative routing.

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