Fetch Sitemap

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

Annotations already mark the tool as read-only; the description adds meaningful behavior: discovery from robots.txt or /sitemap.xml, following sitemap indexes, returning optional lastmod/changefreq/priority, and a credit cost. This goes beyond annotation basics.

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 concise sentences, each adding value: purpose, behavior/return details, and cost/usage preference. No wasted words.

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?

The description covers purpose, behavior, cost, and usage preference, and gives a sense of return content (page URLs with optional metadata). It lacks details on 'limit' behavior, but the schema provides min/max and the overall picture is adequate for a tool with moderate complexity.

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 75%. The description does not add parameter-specific details beyond what the schema provides. The 'limit' parameter lacks a schema description and is not addressed in the text, but the schema covers the other three parameters adequately.

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 clearly states the tool fetches XML sitemap URLs, with a specific verb and resource. It explicitly differentiates from metalift_map by recommending this tool for the site's published URL list.

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?

Provides explicit usage guidance: 'Prefer this over metalift_map when you need the site's published URL list.' This names an alternative and gives a clear condition for use.

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