List Sitemaps

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 says nothing about read-only vs mutating semantics, permissions/auth, pagination, or limits. A single sentence for a bare list operation leaves the agent with little beyond the read-only inference from the verb 'List'.

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 short sentence with no wasted words and the key scope ('submitted for a property') front-loaded. It is efficient, though arguably under-specified rather than tight for a tool with siblings needing differentiation.

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?

An output schema exists, so return values need not be explained, and the core read operation is conveyed. But with no annotations and no usage or behavioral context, the definition is only minimally complete for selecting this tool among its many siblings.

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%, including a well-documented sitemap_index parameter explaining child-sitemap listing, so the schema does the heavy lifting. The description adds no parameter meaning beyond what is already documented, which matches the baseline 3 for high coverage.

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 (List) and resource (sitemaps) scoped to a property, which is clearer than the title alone. However, it does nothing to distinguish itself from close siblings like get_sitemap, submit_sitemaps, or delete_sitemap, so an agent must infer the difference from names alone.

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 tool versus alternatives, nor any prerequisites or exclusions. The agent must guess, for example, that this lists sitemaps while get_sitemap retrieves a single one.

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