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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them — no note on what happens when the sitemap is not found, no auth/scope requirements, and no indication of the shape or size of the returned detail.

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 short sentence with no wasted words and the purpose front-loaded, but it is under-specified rather than economical — brevity here costs the agent information it needs.

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?

This is a low-complexity read tool with a rich annotation set, so the bar is modest, but with no output schema and an undocumented required parameter the description should have specified sitemap_url format and the not-found behavior. As written, the agent can guess the call but not verify it is well formed.

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 only 50%: 'site' is well documented in the schema, but 'sitemap_url' has no description there and the description only implies it identifies the 'submitted sitemap'. The baseline of 3 applies because the schema covers one of the two parameters adequately, but the description fails to compensate for the undocumented sitemap_url (format, whether it must match the submitted URL exactly).

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 gives a specific verb ('Get details') and a specific resource ('one submitted sitemap'), so the agent knows exactly what the call returns conceptually. It stops short of differentiating from the sibling gsc_list_sitemaps, which is why it does not reach 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 rather than gsc_list_sitemaps, or on the prerequisite that the sitemap must already be submitted to the property. The agent must infer the selection rule from the sibling names alone.

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