Scrapiq

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

With no annotations provided, the description carries the full burden. It discloses key behaviors (stripping boilerplate, returning structured fields) but omits details like authentication requirements, rate limits, or error handling. It also doesn't clarify that the operation is read-only, though that's implied. The description is honest but not exhaustive.

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 sentences long, with the primary action and purpose in the first sentence. It is front-loaded with the core functionality and avoids unnecessary elaboration. Every word contributes to the tool's understanding.

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?

The description covers the essential information an agent needs: purpose, behavior, and return values. Since there's no output schema, it explicitly lists the returned fields. It lacks details on authentication, potential failures, or rate limits, but for a straightforward extraction tool with fully documented parameters, this is sufficient.

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% description coverage, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already states (e.g., format, max_chars). It doesn't clarify defaults or edge cases, but that's adequately handled by 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 clearly states the tool's action (extract a web page), the resource (URL), and the intended use case (LLM/RAG pipelines). It also mentions what it removes (boilerplate, navigation, ads, scripts) and what it returns (title, content, links, metadata), making it unambiguous.

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 provides context on when to use the tool (for LLM/RAG pipelines needing clean content) but doesn't explicitly state when not to use it or mention alternatives. Since there are no sibling tools, the usage context is clear enough; however, it lacks explicit exclusions or prerequisites.

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