get_sitemaps

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

No annotations are provided, so the description carries the burden. It conveys a read-only list operation and adds useful behavioral nuance about domain properties covering all subdomains. However, it doesn't disclose response format, pagination, or auth requirements; still, for a simple list tool with an output schema, this is adequate but not rich.

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 a single clear sentence plus a focused Args block. Every sentence adds necessary detail about the parameter. No redundancy or fluff.

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?

With a simple one-parameter input, an output schema, and a clear purpose, the description covers essentials. It could mention the relationship to list_sitemaps_enhanced or get_sitemap_details for full context, but it is largely complete for a straightforward list tool.

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 only defines site_url as a string, and schema description coverage is 0%. The description compensates strongly: it gives the exact format, examples, and explains the distinction between URL-prefix and domain properties. This goes well beyond a 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?

Clearly states it lists all sitemaps for a specific Search Console property. The verb 'List' and resource 'sitemaps' are specific, and the property scope is explicit. It doesn't explicitly differentiate from sibling list_sitemaps_enhanced, so not a 5.

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 a clear prerequisite: use the exact GSC property URL from list_properties. Also explains how to handle domain properties vs subdomains. It doesn't name alternatives like list_sitemaps_enhanced or get_sitemap_details, but the context is clear.

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