webmaster_list_sitemaps

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 behavioral context that the read is cursor-paginated ("using the upstream sitemap identifier cursor"), but reveals nothing about rate limits, ordering, or what a page contains.

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 with no wasted words and the action front-loaded. It is arguably too terse for a four-parameter tool, but as conciseness goes it is efficient.

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 four parameters at 0% schema coverage, a required host_id, and a cursor/parent_id hierarchy unexplained, the description leaves an agent guessing about required inputs and pagination. An output schema exists so return values need not be described, but the input side is materially under-specified.

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 0% for four parameters, so the description must carry the load. It explains the cursor concept ("upstream sitemap identifier cursor") but never clarifies host_id, limit, or parent_id, which is a significant gap.

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 and resource ("Read one sitemap page") plus the mechanism (cursor-based paging), so the action is understandable. However it does not distinguish this from close siblings like webmaster_get_sitemap or webmaster_list_user_sitemaps, and the singular "one sitemap page" sits awkwardly against the plural list_ name, leaving mild ambiguity about whether it returns sitemaps or pages.

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 statement of when to use this versus webmaster_get_sitemap, webmaster_list_user_sitemaps, or the prepare/apply sitemap siblings. No prerequisites (e.g. host_id requirement) or exclusion conditions are given.

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