get_sitemaps

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

No annotations are provided, so the description must cover behavioral traits. It discloses the action (listing) but does not state whether this is a read-only operation, what permissions are needed, or any side effects. For a listing tool, the description should at least imply it is non-destructive.

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 highly concise: two sentences plus a brief argument block. Every part is necessary and adds value. There is no superfluous text.

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 (one parameter), and an output schema exists, so the description need not detail return values. The description covers the parameter well and provides context about domain properties. A perfect score would require mentioning that the tool lists all sitemaps (including state), which it does, so the slight deduction is for not explicitly stating that it is read-only.

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 description compensates for the lack of schema description coverage by thoroughly explaining the site_url parameter, including examples, format requirements, and important domain property behavior. This adds significant value beyond the 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 uses a specific verb and resource: 'List all sitemaps for a specific Search Console property.' This clearly communicates the action and scope, and distinguishes it from siblings like 'list_sitemaps_enhanced' or 'get_sitemap_details' by focusing on the basic listing for a given property.

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 detailed usage guidance, including the exact format of site_url and notes on domain property behavior (covers all subdomains, use domain property and filter by page for specific subdomain analysis). However, it does not explicitly state when to use this tool versus alternatives such as 'list_sitemaps_enhanced'.

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