create_kb_from_urls

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

The description adds important behavior beyond annotations: scraping is asynchronous and callers should poll list_kb_docs/get_kb_doc. It also clarifies the KB router scrape and default scrapeContent behavior. It does not cover permission requirements, rate limits, or partial-failure behavior, but annotations already communicate mutation/open-world/non-idempotent traits.

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 dense but front-loaded and highly efficient. Each sentence carries routing, mode, async, or anti-pattern information without filler.

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?

For a complex, non-idempotent, open-world ingestion tool with no output schema, the definition covers the core workflow, alternative tools, modes, and async polling. It leaves some secondary parameter behavior and failure/partial-success handling to the schema and annotations.

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 high, but the description still adds useful meaning by explaining that per_url creates one KB doc per URL while batch makes a single API call with urls[]. It reinforces the 50-URL cap and scrapeContent behavior. Remaining parameters such as tags, metadata, refreshRate, and skipExisting are covered mainly 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 states a specific verb and resource: adding many website pages to an agent KB via URL ingestion. It explicitly positions itself as the preferred tool for this task and distinguishes itself from scrape_url/create_kb_doc workflows.

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 gives explicit when-to-use guidance, names a clear anti-pattern (web-fetch/scrape_url then paste into create_kb_doc), and points to alternatives for whole-site ingestion (create_kb_doc sourceType=sitemap). It also explains per_url vs batch modes.

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