list_sitemaps_enhanced

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

No annotations are provided, so the description bears the burden of behavioral disclosure. It does add meaningful behavioral context: domain properties cover all subdomains, and sitemap_index lists child sitemaps. It does not mention auth requirements, rate limits, or explicitly confirm that the operation is read-only, though 'List' suggests it.

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 well-structured and reasonably concise, front-loading the purpose and then providing an Args section. Every sentence adds signal, though 'with detailed information' is somewhat vague and could be omitted without loss.

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 the tool's moderate complexity, the output schema is available, and both parameters are clearly documented, the description is largely complete. The main gap is the lack of explicit guidance on when to use this tool instead of the overlapping get_sitemaps or get_sitemap_details siblings.

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 description coverage is 0%, so the description must fully compensate for parameter meaning. It does: site_url is explained with exact formatting examples and linkage to list_properties, including domain-property nuance, and sitemap_index is described as an optional sitemap index URL for listing child sitemaps. This is strong, complete parameter documentation.

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 states a specific action and resource: 'List all sitemaps for a specific Search Console property with detailed information.' This clearly conveys what the tool does. However, it does not explicitly distinguish itself from the sibling get_sitemaps or get_sitemap_details tools beyond the word 'enhanced' and 'detailed information.'

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 gives useful usage context for the site_url parameter, instructing users to use an exact GSC property URL from list_properties and explaining how domain properties behave. It does not, however, say when to choose this tool over siblings like get_sitemaps or get_sitemap_details, so tool-selection guidance is only implied.

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