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

No annotations are provided, so the description carries the full burden. It discloses the read-oriented extraction behavior, the 'current page' scope, and the optional CSS selector restriction. However, it does not mention any side effects, prerequisites like a loaded page, error behavior, or how it interacts with dynamic content.

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?

The description is two compact sentences with no filler. It front-loads the main purpose, then a useful optional behavior, then the use context. Every clause adds information relevant to selecting and invoking the tool.

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 simple two-optional-parameter tool, no output schema, and no annotations, the description is largely complete: it explains the output formats, the selector behavior, and the intended use case. It is missing only finer caveats about return structure or DOM dependencies, but these are minor for this tool.

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%, so the baseline is 3. The description adds meaningful value by specifying that the selector limits extraction to a region and by clarifying what the structured JSON contains (title, body, tables, links), going beyond the schema's sparse parameter descriptions.

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 uses a specific verb ('extract') with a clear resource ('current page content') and explicitly lists output forms (markdown/structured JSON) and content types (title, body, tables, links). It also distinguishes this from navigation and interaction sibling tools by framing it as the core tool for scraping agents.

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?

It clearly states this is the core tool for collection/scraping agents, giving a clear context for when to use it. It does not explicitly mention when not to use it or compare it with sibling alternatives, but the extraction-specific framing provides adequate guidance.

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