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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds useful content about what the payload contains (errors, warnings, read dates, submitted vs indexed counts), but says nothing about scope, freshness, pagination, or what happens when the site is ambiguous — even though the schema notes the site param is required when multiple sites are enabled.

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 front-loaded sentence fragment listing exactly the fields returned, with zero padding. It is efficient, though the missing verb makes it read as a label rather than a statement of what the tool does.

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 no output schema, the description does valuable work by enumerating the returned fields. However, for a read tool it is thin: it does not state that the result is a list per site, does not hint at row volume or the summary/full trade-off, and does not reference the sibling write tools an agent will likely need next.

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 100% and both enums are documented in-schema, so the schema carries the burden; baseline 3 applies. The description adds no meaning beyond it — it never mentions site scoping, the summary/full detail toggle, or language/folder behavior.

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 names a specific resource (submitted sitemaps) and enumerates the fields returned: status, last read date, errors, warnings, submitted vs indexed URL counts. That is enough to tell it apart from gsc_submit_sitemap and gsc_remove_sitemap by implication, but it is a noun phrase rather than a verb phrase ('Lists...') and never explicitly states it is the read/report counterpart to those write siblings.

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?

There is no when-to-use guidance at all: no mention of when to check sitemap health versus running gsc_sites, gsc_inspect_url, or gsc_submit_sitemap, and no exclusions. The only usage steering in the whole definition lives in the schema's 'detail' enum description, which is structured data the description itself does not reinforce.

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