list_sitemaps

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

No annotations are provided, so the description carries full burden. It warns against speculation and instructs citing site_url+date_range, but does not disclose whether the tool has side effects, authentication requirements, rate limits, or the nature of the output (e.g., only new sitemaps, etc.). The mention of date_range is confusing since the input only has site_url.

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?

The description is two sentences: the first states purpose, the second gives an important usage constraint. It is efficient and front-loaded, with no wasted words.

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?

Given the tool has one required parameter, no output schema, and no annotations, the description should be more thorough. It does not explain what the returned data looks like, whether it is paginated, or if there are limits. The warning is about data usage, not about the tool's overall behavior.

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%, meaning the parameter site_url has no description in the schema. The description does not explain what site_url is (it only says 'for a property'), nor does it provide format or constraints. It adds minimal value beyond the schema.

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 starts with 'List sitemaps submitted for a property, with errors/warnings/last-submitted info,' which is a specific verb+resource. It clearly distinguishes from sibling tools like list_sites (lists sites) and submit_sitemap (submits a sitemap).

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 description includes an important warning about using only returned data and citing site_url+date_range, but it does not explicitly state when to use this tool versus alternatives, nor when not to use it. Usage is implied but not guided.

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