pristine_marketplace_sitemap_urls

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

No annotations are provided, so the description carries the full burden. It discloses two behaviors: results are 'capped' (implying a limit) and the storefront URL is fixed server-side. It does not mention pagination, response format, error handling, or authentication. While adequate for a simple list tool, it leaves gaps in behavioral detail.

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 two sentences, front-loaded with the primary action, and contains no redundant phrases. It efficiently conveys the purpose, source, and a key constraint without unnecessary detail.

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 a tool with two optional parameters and no output schema, the description covers the essentials: what it does, the source domain, and the fixed URL constraint. It does not explain the return format in detail, but given the simplicity, this is not a significant gap. It could mention the relationship to sibling sitemap tools, but that's more about usage guidance.

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 input schema describes both parameters (type with enum values, limit with default and max). The description adds minimal semantic value beyond the schema, only implicitly referencing the type parameter. Since schema coverage is 100%, a baseline of 3 is appropriate; the description does not exceed that.

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 verb (List) and resource (Pristine Marketplace sitemap URLs), and specifies that it returns entries from child sitemaps. This distinguishes it from sibling tools like pristine_marketplace_sitemaps (which likely returns the parent sitemap index) and product-specific tools. The reference to the storefront URL being fixed server-side adds clarity about scope.

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 provides clear context: it lists URLs from child sitemaps filtered by type. However, it does not explicitly mention alternative tools (e.g., pristine_marketplace_sitemaps) or when not to use this tool. It gives context but lacks explicit exclusions or alternatives.

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