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 the paid cost ($0.002), the crawl scope (1-hop same-host), and the maxUrls limits (up to 50, default 20). However, it does not state return format, error behavior, or whether the crawl is synchronous, which would help an agent set expectations.

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, dense sentence front-loads the most important signal (cost) and packs crawl scope and parameter limits efficiently. There is zero filler; every clause carries operational meaning.

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 no annotations and no output schema, the description conveys cost, scope, and limits but omits return value shape and failure semantics. For a tool with only two simple parameters and a narrow crawl scope, this is mostly adequate, but the lack of any statement about what the tool returns leaves a moderate gap.

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 both parameters (url, maxUrls) are described in the schema. The description adds the default value (20) and the range semantics (1-50), which slightly augments the schema's '1-50 (default 20)' but does not add significant new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 (map/crawl) and resource (site URL list from sitemap/robots plus a 1-hop same-host crawl). It clearly states what the tool produces and distinguishes itself from siblings like capture, analyze, and preview by focusing on URL discovery. However, the term 'map_lite' is not fully unpacked, so some differentiation relies on the tool name.

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 implies usage context (URL discovery from sitemap/robots) but gives no explicit when-to-use vs. alternatives guidance. It does not name siblings or state conditions that would select webcap_map_lite over webcap_capture or webcap_extract. The cost prefix hints it is a paid entry point, but no exclusions or alternatives are mentioned.

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