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

No annotations are provided, so the description carries the full behavioral burden and falls short. It does not disclose whether pages are JS-rendered, whether authentication or rate limits apply, what happens when the selector matches nothing, or what 'metadata' concretely includes.

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 tight sentence with no filler and the action front-loaded. It is efficient, though the brevity edges toward under-specification rather than disciplined conciseness.

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 no output schema and no annotations, the description is the only source of behavioral information, and it leaves key questions unanswered: what 'metadata' is returned, the shape of results, and error behavior. For a two-parameter extraction tool the coverage is thin.

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 coverage is 100% with two well-described parameters, so the baseline is 3. The description's mention of 'selector content' loosely corroborates the selector parameter but adds no format, syntax, or fallback semantics beyond the schema.

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 resource (metadata or targeted selector content from a webpage), which is far clearer than a tautology. However, it never distinguishes itself from its siblings scrape and batch_scrape, so an agent must infer the boundary between plain scraping and targeted extraction.

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?

There is no when-to-use guidance and no mention of the sibling tools scrape or batch_scrape, even though they clearly overlap. The word 'specific'/'targeted' faintly implies a selective use case, but nothing tells the agent when to pick this over scrape.

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