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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description still adds genuine behavioral context beyond that: no JavaScript execution (so client-rendered pages return nothing useful) and no access-restriction bypass. It doesn't discuss rate limits or failure behavior, keeping it below 5.

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?

Two sentences, no filler, with the extracted-output list front-loaded and the limitations second. Every clause carries information an agent needs; nothing is padded.

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?

With one required parameter, no output schema, and complete annotation coverage, the description carries the remaining burden and does so by enumerating what comes back (text, Markdown, headings, links, tables) and the two hard limits. Missing only marginal detail such as pagination or whether redirects/large pages are handled.

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 100% and the single URL parameter is fully documented in the schema (type, range, length limit, HTTP/HTTPS constraint). The description adds no syntax, format, or constraint detail beyond that, so the baseline 3 applies.

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 names a specific verb ('Extract') and enumerates the resources produced (readable text, Markdown, headings, HTTP links, tables) from 'one accessible public webpage'. That is precise and distinguishable from most siblings, though it never names tablelift_extract_tables, the closest overlapping sibling, so differentiation is only implicit.

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?

'one accessible public webpage' plus 'Does not execute JavaScript or bypass access restrictions' effectively states when the tool will and will not work, which is real usage context. It stops short of a 5 because no alternative tool is ever named for JS-rendered pages or gated content.

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