list_sitemaps_enhanced

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

With no annotations, the description carries full burden. It adds useful parameter context (e.g., site_url format, domain property note) but does not disclose side effects, auth requirements, rate limits, or what 'detailed information' includes. Adequate but not comprehensive.

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?

Two main sentences plus parameter descriptions. Front-loaded with purpose, no fluff. Each sentence adds value. Could be slightly improved by explicitly stating enhanced nature up front, but overall efficient.

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?

Given sibling tools and output schema existence, the description covers parameters well and hints at enhanced detail but does not fully guide tool selection. Lacks comparison to get_sitemaps and does not mention what 'detailed information' includes. Adequate but with gaps.

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%, but the description provides excellent semantic information for both parameters. site_url includes format examples and domain property guidance; sitemap_index explicitly explains its purpose. This compensates fully for the missing schema descriptions.

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 sitemaps for a specific GSC property with detailed information. The verb 'list' and resource 'sitemaps' are specific. It distinguishes from siblings by hinting at enhanced detail and optional child sitemap listing, but could explicitly contrast with get_sitemaps.

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: requires site_url from list_properties, explains domain property behavior, and descriptions of sitemap_index. However, no explicit guidance on when to prefer this over get_sitemaps or manage_sitemaps, nor 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.