sitemap_parse

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

Discloses no side effects, error conditions (unreachable URL, invalid XML), and behavior for both sitemap types. Explains maxUrls limit and its effect. With no annotations, the description fully covers behavioral 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?

Three clear sentences: main function, error handling, use cases. Front-loaded with primary purpose. No unnecessary words. Each sentence serves a distinct purpose.

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 two parameters, no output schema, and no annotations, the description is quite complete. It explains input, return format, errors, and use cases. Minor omission: exact JSON structure not fully described, but the mention of fields suffices.

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 baseline is 3. The description adds extra value by specifying default (100) and max (1000) for maxUrls, and clarifying it has no effect on sitemapindex. This goes beyond schema details.

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?

Clearly states it fetches and parses XML sitemaps, returning structured JSON for urlset or sitemapindex. Distinguishes itself from generic fetch tools by specifying its exact purpose: enumerating pages, finding updated content, building crawl queues.

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 lists use cases (enumerate pages, find updated content, build crawl queue). Implicitly suggests not to use for raw HTML fetching. However, does not explicitly mention when not to use or compare to siblings, though the context makes it clear.

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