gsc_list_sitemaps

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

No annotations are provided, so the description must carry the full burden. It states what the tool does and the fields returned, but does not explicitly mention read-only behavior, authentication requirements, or any side effects. The verb 'List' implies safety, but additional context would be helpful.

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?

A single, efficient sentence that is front-loaded with the action and resource, with no redundant words.

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?

For a simple one-parameter tool with no output schema, the description provides key return values (status, last download date, URL counts) which helps the agent understand what to expect. Minor gap: schema marks siteUrl as not required, and the description doesn't clarify whether it must be provided.

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 100% and the parameter description in the schema ('Use gsc_list_sites to find available sites') is helpful. The tool description itself adds no extra parameter meaning, so baseline 3 is appropriate.

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-object pairing ('List all sitemaps') and specifies the resource (sitemaps submitted for the site). It clearly distinguishes from sibling tools like gsc_list_sites (lists sites) and gsc_search_analytics (search data).

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 implies usage context (needs a siteUrl) and the parameter schema explicitly directs users to gsc_list_sites to find available sites, providing a cross-reference. However, it does not explicitly state when not to use this tool or name alternatives besides that hint.

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