Sitemap URL Extractor

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

No annotations are provided, so the description carries the full disclosure burden. It does add one useful behavioral fact — the result is one row per page URL — but says nothing about async/actor execution, what happens when a site has no sitemap, whether sitemap discovery goes through robots.txt, or truncation 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 front-loaded sentence with no filler; the action and the return granularity are both stated immediately.

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 simple three-parameter tool with full schema coverage and no output schema, the description covers purpose and return granularity. It is still thin on operational behavior — sitemap discovery method, empty-result handling, and the fact that maxUrls defaults high — which an agent would want before calling it.

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 description coverage is 100%, and the schema itself explains maxUrls (sampling cap), startUrls (website or sitemap URLs), and waitSeconds (Apify run wait). The description adds no parameter meaning beyond that, which is the expected baseline when the schema is fully documented.

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 names a specific verb+resource ('Find sitemap URLs') and states the output shape ('one row per page URL'), which distinguishes it from all siblings in the SEO/scraping family. Minor ambiguity: it says it finds sitemap URLs but returns page URLs, so the agent must infer that pages are extracted from discovered sitemaps.

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 explicit when-to-use guidance, no mention of alternatives such as the sibling seo-audit-ai-search-readiness tool, and no stated prerequisites (e.g., whether the site must have a sitemap or robots.txt). Usage is only implied by the verb 'Find sitemap URLs'.

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