list_sitemaps_enhanced

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 important behaviors: sitemap_index lists child sitemaps, and domain properties cover all subdomains. However, it doesn't mention authentication, rate limits, or behavior when no sitemaps are found, leaving some gaps.

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 concise and well-structured: a one-sentence summary followed by a focused Args list. Every sentence adds value, with no filler or repetition of schema 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?

The tool has an output schema, so return values are already specified. The description adequately covers both parameters and domain property nuances. It could have further referenced the sibling 'get_sitemaps' for differentiation, but overall it is complete for a list tool with a schema.

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 descriptions are completely absent (0% coverage), so the description must compensate. It does this well: site_url is defined with examples and source, and sitemap_index is explained as optional and for listing child sitemaps, adding meaningful semantics 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 all sitemaps for a specific Search Console property with detailed information, using a specific verb and resource. It implies a distinction from siblings like 'get_sitemaps' through 'detailed information' but does not explicitly name alternatives.

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 clear usage context: site_url must be an exact GSC property URL from list_properties, with examples. It explains domain property behavior and suggests how to target subdomains, but does not explicitly contrast with alternative sitemap tools or state when not to use it.

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