sitemaps_list

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the action without disclosing side effects, permissions, or limitations (e.g., whether it requires authentication, if it returns all sitemaps, or if pagination exists). This is insufficient for a read operation.

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 extremely short (one phrase) but efficient for the tool's purpose. No unnecessary words are included. However, it could benefit from slightly more detail without becoming verbose.

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 no output schema and no annotations, the description lacks information about return values, such as whether it returns a list of sitemap URLs or metadata. Additionally, given the large set of sibling tools, the missing context reduces usefulness.

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?

Both parameters (siteUrl and engine) are fully described in the input schema (100% coverage). The description does not add any additional information beyond the schema, so baseline score of 3 is appropriate.

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 'List sitemaps for a site' clearly states the action (list) and resource (sitemaps), with a specific parameter (siteUrl). It effectively distinguishes from sibling tools like sitemaps_get, sitemaps_submit, and sitemaps_delete.

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 implies that the tool is for retrieving a list of sitemaps, but it does not explicitly state when to use it versus alternatives like sitemaps_get. No usage context, when-not, or alternative tool references are provided.

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