Map Website

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

Annotations already declare read-only, open-world, non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context: it does not fetch page content, large sites can overflow context, and the default limit is 10. It does not explain sitemap/domainFilter behavior, but it meaningfully exceeds the annotations.

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?

Three compact sentences, front-loaded with the core operation and immediately followed by the context-overflow caveat and workflow guidance. No sentence is redundant.

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 an 8-parameter tool with no output schema but full schema descriptions, the description provides the essential mental model and workflow. It omits details about sitemap modes, domainFilter, and geo/locale, but those are fully documented in the schema, so the description is largely complete.

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 100%, so the schema documents all parameters. The description still adds semantic value by explaining why limit defaults to 10 (context overflow) and why selectPaths/excludePaths should be used to narrow results, rather than merely restating 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?

States a specific verb and resource: list URLs on a website without fetching their content. The phrase 'without fetching their content' clearly distinguishes it from scrape_as_markdown and crawl tools, so an agent can select it without opening the schema.

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?

Explicitly recommends the workflow: 'map the site, then scrape_as_markdown only the pages you need', naming the alternative and the condition that selects it. It also explains when to narrow with selectPaths/excludePaths, leaving little inference.

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