Searchconsole.Sitemaps.List

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: not whether a verified/search-console-authorized property is required, not whether sitemap indexes and child sitemaps are both returned, and not how an empty result set behaves. The presence of an output schema covers return shape, but permission and scope behavior remain undocumented.

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?

One sentence, front-loaded with verb and resource, with no filler. It is efficient, though the terseness is achieved by omitting information rather than by disciplined editing.

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 an output schema, the minimum is nearly met, but the site_url format ambiguity and the absence of any authorization or scope note leave real gaps an agent would hit on first invocation.

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% and the single required parameter site_url is undocumented anywhere. The phrase "for a property" hints that site_url identifies the property, but it does not give the critical format (URL-prefix like https://example.com/ versus sc-domain:example.com), which materially affects whether the call succeeds.

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 sitemaps") plus scope ("for a property"), so an agent can tell this is the read counterpart to searchconsole.sitemaps.submit and searchconsole.sitemaps.delete. Sibling differentiation comes only from the verb, not from any explicit statement, so it stops 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 when-to-use guidance, no mention of the submit/delete siblings, and no stated prerequisite such as needing a verified property. The agent must infer usage entirely from the verb.

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