get_sitemaps

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context about how domain properties behave, but does not disclose whether the operation is read-only, permissions needed, rate limits, or what the response contains. This leaves significant gaps for a tool with no annotation safety hints.

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, with a clear first sentence and a focused Args block that provides necessary parameter details without unnecessary fluff. 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 tool is simple with one parameter and has an output schema, so the description need not explain return values. It covers the main functional purpose and parameter semantics well, but lacks information about when to use this vs. the 'list_sitemaps_enhanced' sibling, which would make it more complete.

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%, and the description fully compensates by explaining site_url with concrete examples, the format (URL or sc-domain), and guidance on using domain properties for subdomain analysis. This adds substantial meaning beyond the bare 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 that the tool lists all sitemaps for a specific Search Console property, using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like list_sitemaps_enhanced or get_sitemap_details, so it is slightly below top marks.

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 provides some usage context by explaining how to specify site_url, including the distinction between domain and URL properties, and recommends using the domain property and filtering by page for subdomain analysis. However, it does not explicitly state when to choose this tool over alternatives or mention any exclusions.

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