map_url

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

With no annotations, the description discloses the key behavior of not fetching full page content, that it returns a list of URLs, and that it crawls with configurable depth/limit and include/exclude patterns. It clearly states it 'discovers' URLs, implying a read-only operation.

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 well-structured with a clear intro, best-for list, typical workflow, and concise args explanations. Each sentence adds value; no wordiness.

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?

With an output schema present, the description doesn't need to explain return values. It covers purpose, usage context, parameter semantics, and behavior comprehensively, making it complete for an agent to select and invoke the tool.

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 description provides a detailed Args section that explains every parameter, including the meaning of limit, depth, include_subdomains, include_external_links, include_patterns, and exclude_patterns, with an example wildcard for include_patterns. This fully compensates for the 0% schema coverage.

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 'Discover URLs on a website without fetching full page content' and 'Returns a list of URLs found by crawling from the starting URL.' This clearly identifies the resource (website URLs) and specific verb (discover), and distinguishes it from sibling tools like scrape_url, which fetches content.

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 says 'Use this to find the right page before scraping it' and includes a 'Typical workflow: map_url to find URLs -> scrape_url on the right page.' It also lists best-for use cases, providing clear guidance on when to use and an alternative.

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