Show Sitemaps

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds value the annotations cannot: it discloses the shape of the payload an agent will get back (status, URL counts, errors, warnings), which matters because no output schema exists. It does not mention pagination or auth/scope requirements.

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?

Two short sentences, zero filler, with the core behavior front-loaded and the optional parameter path immediately after. Nothing is repeated or padded.

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 two-parameter read-only listing tool with no output schema, the description covers purpose, the optional index-expansion mode, and the returned fields. The only remaining gap is that the site_url property's domain-property nuance lives solely in the schema rather than the description, which is a minor omission.

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 description coverage is 100%, so both parameters are already documented in the schema, including sitemap_index as "Optional sitemap index URL to list child sitemaps." The description's mention of sitemap_index largely restates the schema, and site_url is not addressed at all, so the baseline 3 applies.

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 and resource ("List submitted sitemaps") and enumerates what is returned (status, URL counts, errors, warnings), which separates it from the singular wsp_show_sitemap_gsc and the mutation siblings wsp_add_sitemap_gsc/wsp_remove_sitemap_gsc. It stops short of naming an alternative explicitly, so a 4 rather than 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?

The second sentence gives real guidance for one path: pass sitemap_index to enumerate an index's children. There is no statement of when to prefer this over wsp_show_sitemap_gsc or when not to use it, so usage is only partially implied.

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