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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that the response carries status detail (last submitted, errors/warnings, pending), which is useful orientation, though it overlaps with the available output schema and says nothing about pagination or empty-list behavior.

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 beginning with the verb, with the returned status fields appended compactly. No filler or restated naming.

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 one-parameter read tool with full annotations and an output schema, the description covers purpose and the shape of what comes back. The only real gap is the site_url format, which matters for a Search Console property identifier.

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 0% and there is one parameter, site_url. The phrase 'submitted to a property' loosely signals that the parameter identifies the property, but the description does not state the expected format (full URL vs. sc-domain: form) or that it must match a gsc_list_sites entry.

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?

States a specific verb ('Lists') and resource ('sitemaps submitted to a property') and scopes it via the property. 'Lists' inherently separates it from the write siblings gsc_submit_sitemap and gsc_delete_sitemap, so an agent can route correctly without opening schemas.

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 verb 'Lists' implies this is the read/inspect path when checking sitemap state, but the description never states when to prefer it over gsc_submit_sitemap, gsc_delete_sitemap, or gsc_inspect_urls, nor any prerequisites (connected property, verification). Usage is inferable rather than stated.

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