seo_sitemap_generator

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

The description claims to validate against Google limits and emit a sitemap index when needed, but it also mentions 'hreflang alternates' which are not present in the input schema. Without annotations, the description carries the full burden but is inconsistent with the schema, reducing transparency.

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 a single paragraph that repeats 'Sitemap Generator' and includes 'Menu ID' which adds no value. It could be more concise by removing redundancy and focusing on essential details.

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?

No output schema or annotations are provided. The description does not explain the return format, and the parameter inconsistencies undermine completeness. For a tool with 2 required parameters and no output schema, more detail is needed.

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 0%, so the description must compensate. However, it describes 'lastmod, changefreq, priority' as optional while the schema lists them as required, and it mentions 'hreflang' which is not in the schema. The required parameter 'prettyPrint' is not mentioned at all. This is contradictory and misleading.

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 it generates an XML sitemap from a list of URLs with optional attributes, specifying compliance with sitemaps.org and Google Search Console limits. It distinguishes itself from sibling SEO generation tools, though the inclusion of 'Menu ID: sitemap_generator' is redundant.

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 implies usage for generating sitemaps but does not explicitly state when to use it versus alternatives or when not to use it. The mention of 'Use describe_tool ... for full page guidance' suggests additional documentation exists, but the description itself lacks direct guidance.

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