gate402_scrape

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

The description discloses key behaviors: rendering client-side JS, stripping nav/ads, and returning Markdown. It also mentions pricing and free tier. However, it omits details like rate limits, error handling, or authentication requirements, which are important for a web scraping tool.

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 concise sentences: the first describes the core functionality, the second adds pricing context. No wasted words, front-loaded with key purpose.

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 no annotations and no output schema, the description covers the main purpose, input, process, and output format. Missing error cases and size limits, but adequate for typical use.

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?

The input schema has 100% coverage with the 'url' parameter description. The tool description adds no new meaning beyond the schema's 'Public URL'. Baseline is 3 per rules.

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 clearly states the tool fetches any public URL, renders client-side JS, strips nav/ads, and returns clean LLM-ready Markdown. It distinguishes from siblings like gate402_scrape_stealth by emphasizing the non-stealth nature and explicit pricing.

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 explicitly says 'Fetch any public URL', providing clear context for when to use. However, it does not mention when not to use or provide alternatives among siblings, such as gate402_scrape_stealth for stealth scraping.

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