shopify_sitemaps

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

No annotations are provided, so the description bears full responsibility. It mentions the source path and inferred types, but lacks details on error conditions, required permissions, or data freshness. The behavior is partially clear but insufficiently transparent.

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 extremely concise: one sentence describing the action and a second clarifying the return. Every word is purposeful, with no redundancy or unnecessary elaboration.

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 explains the tool's purpose and output (child sitemap URLs with types), but lacks details on the output structure (e.g., format, whether it's a list or tree). Given no output schema, more completeness would be beneficial. Adequate but not thorough.

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 parameter 'url' is described in the schema as 'Shopify storefront URL', and the tool description adds that it accesses the public /sitemap.xml index. With 100% schema coverage, the baseline is 3, and the description adds marginal value beyond 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?

The description clearly states the tool lists Shopify sitemaps, specifying it returns child sitemap URLs from the public /sitemap.xml index with inferred types. This provides a specific verb and resource, and implies a distinction from sibling tools like shopify_sitemap_urls, but does not explicitly differentiate.

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?

No guidance is provided on when to use this tool vs alternatives. It does not mention prerequisites, context, or when not to use it. The description simply states its function without usage direction.

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