get_sitemaps

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds the useful nuance that domain properties cover all subdomains, but it does not mention pagination, limits, response format, or explicitly confirm read-only behavior. 'List' implies a read operation, but that is not enough for full transparency.

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 front-loaded with a clear one-sentence purpose followed by a tight parameter note. The domain-property caveat is valuable and there is no filler or redundant restatement of the tool name.

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 single-required-parameter tool with an output schema, the description thoroughly explains the only parameter and how to obtain it. It does not explicitly route the agent to list_sitemaps_enhanced when richer sitemap data is needed, but that is a differentiation gap rather than a correctness gap.

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 0% description coverage, but the description compensates well. It explains that site_url must be an exact GSC property URL, gives concrete examples including sc-domain:example.com, and explains how domain properties cover subdomains. This adds substantial meaning beyond the bare schema definition.

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 states a specific action and object: 'List all sitemaps for a specific Search Console property.' It clearly identifies what the tool does and its scope, but it does not explicitly distinguish itself from sibling tools like list_sitemaps_enhanced or get_sitemap_details.

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 a concrete prerequisite (use site_url from list_properties) and explains property URL formats, but it never states when to prefer this tool over list_sitemaps_enhanced or get_sitemap_details. Usage context is implied by the simple listing action rather than explicitly contrasted with alternatives.

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