list_sitemaps_enhanced

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It implies a read-only operation through 'List', but does not explicitly state safety, permissions, rate limits, or side effects. It does add useful behavioral context about domain properties covering subdomains, which is a notable positive.

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 very concise, front-loaded with a clear purpose statement, followed by efficient parameter documentation. No filler or redundant information, every sentence earns its place.

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 description covers parameters well and the presence of an output schema means return values are already documented. The main gap is the lack of alternative tool references, but for the tool's simplicity, the information provided is sufficient for correct invocation.

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?

The schema has zero description coverage, but the description thoroughly explains both parameters: site_url with concrete examples and domain property behavior, and sitemap_index as the optional index to list child sitemaps. This fully compensates for the schema's lack of 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 Search Console property with detailed information. The verb 'List' and resource 'sitemaps' are specific, but it does not explicitly distinguish itself from sibling tools like get_sitemaps or get_sitemap_details, so it misses the top score.

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 clear parameter usage guidance, such as site_url format and that domain properties cover all subdomains. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or when-not to use, leaving usage implied rather than explicit.

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