list_available_scrapers

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

No annotations. The description mentions that plugin scrapers show automatically, which is a key behavior. However, it lacks details on read-only nature, rate limits, or permissions, which are acceptable for a simple listing.

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, front-loaded with key purpose. No filler, every sentence earns its place.

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 zero parameters and an output schema, the description covers purpose, plugin registration, and usage guidance. Missing explicit mention of built-in scrapers, but it's implied.

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?

No parameters, so baseline 4. The description adds no param info, but none is needed as schema coverage is 100% and params are absent.

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 specifies 'list every scraper available to this server,' which is a clear verb and resource. It distinguishes from sibling tools like scrape_with and specific scrapers.

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 explicitly states 'Use a returned name with scrape_with,' providing direct guidance on when to use this tool. It could add when not to use, but the recommendation is strong.

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