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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful context about what the response contains (last crawl, errors, warnings, URL count), but says nothing about ordering, volume, or auth/scope requirements beyond what annotations give.

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 tight sentence that front-loads the resource and then lists the salient return fields. No filler, though it omits an explicit verb phrase that the title supplies.

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?

No output schema exists, and while the description sketchily covers return contents, it leaves the one required parameter's format and any pagination/ordering behavior unspecified. Adequate but with clear gaps for a tool with an undocumented input.

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 single required parameter site_url has 0% schema description coverage, so the description carries the full burden and fails to describe it. It only alludes to 'a Search Console site' without giving the expected property format (e.g. URL-prefix vs sc-domain:).

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 (sitemaps submitted for a Search Console site) and enumerates the returned fields (last read date, errors, warnings, URL count), which combined with the title makes the operation unambiguous. It does not explicitly differentiate from the sibling gsc_submit_sitemap, keeping it just short of a 5.

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 guidance on when to use this tool versus alternatives like gsc_submit_sitemap or gsc_query. The agent must infer that listing submitted sitemaps is a distinct read action from submitting one.

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