seo_sitemap_analyze

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'parses URLs, validates format, and identifies SEO issues,' which is useful, but doesn't disclose output format, potential side effects, rate limits, or whether it fetches the URL remotely. For an external fetch/analysis tool, this is a notable gap.

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 main purpose and followed by specific examples of what it checks. Every sentence adds value, and it's appropriately concise.

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 annotations, no output schema, and only partial parameter documentation. For a tool that fetches and parses an external URL, an agent would benefit from knowing what response format to expect, whether a domain (not just a sitemap URL) is accepted, how maxUrls behaves, and potential errors (e.g., invalid sitemap format). The description covers the 'what' but not the 'how' or 'what to expect'.

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 50%: url is described, maxUrls is not. The description says 'URL limits' as an SEO issue, but doesn't explain what maxUrls controls (likely cap on parsed URLs). The description adds some context about what the tool examines, but doesn't fully compensate for the undocumented maxUrls parameter.

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?

Description clearly identifies the action (Analyze), resource (XML sitemap), and specific concerns (URL validation, SEO issues like missing lastmod or URL limits). It distinguishes from sibling tools like seo_robots_analyze, but doesn't explicitly name siblings, so it lacks direct differentiation.

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?

Description implies use when analyzing a sitemap but does not state when to choose this over seo_robots_analyze or other SEO analysis tools. The input schema 'url' description says 'Sitemap URL or domain', which adds some usage context, but no explicit when-to-use or alternative guidance is provided.

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