netintel_og_scraper

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

No annotations are supplied, so the description carries the full behavioral burden, and it does little more than list outputs. It does not say whether the page is fetched server-side, whether redirects are followed, whether JavaScript-rendered content is handled, or what happens on non-HTML or non-public targets. "Any public URL" hints at scope but gives no failure or rate-limit behavior.

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 dense sentence with the verb front-loaded and no filler. The enumeration of return fields is long but each item earns its place given there is no output schema.

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 annotations, no output schema, and 0% parameter coverage, the description partially compensates by enumerating the extracted fields, which effectively documents the return contents. However it is silent on permissions, fetch/render behavior, error modes, and how it differs from sibling extraction tools, leaving real gaps for a no-annotation 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?

There is a single parameter (url) with 0% schema description coverage, so the description must compensate. "From any public URL" weakly conveys that the parameter is a fetchable absolute URL and implies public-only targets, but it does not specify scheme requirements, format, or handling of malformed input. Marginal value over the self-evident parameter name.

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") and enumerates exactly which artifacts are retrieved (OG tags, Twitter Cards, canonical URL, JSON-LD, article metadata). An agent knows precisely what this tool produces. However, it never distinguishes itself from near-siblings like netintel_page_extract, netintel_markdown, or netintel_web_fetch, which likely overlap heavily.

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 or when-not-to-use guidance and no mention of alternatives among the many extraction/scraping siblings. The only implied usage cue is "any public URL," which the agent must infer means social-preview metadata retrieval rather than general page content extraction.

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