list_sitemaps_enhanced

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool lists sitemaps with detailed info, but does not mention that this is a read-only operation, any side effects, error conditions, or rate limits. The behavioral traits are insufficiently disclosed.

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 very concise: one sentence for purpose, followed by bullet-like parameter explanations. Every sentence adds value and is front-loaded. No redundant or verbose content.

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 simple two-parameter tool and existence of an output schema, the description is fairly complete. However, it lacks explanation of what 'detailed information' means, and does not address pagination or limits. Surfficient for a basic list operation but could be more informative.

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%, but the description provides meaningful explanations for both parameters: site_url is explained with examples and domain property usage, sitemap_index is explained as optional for child sitemaps. This adds significant value beyond the schema, though could include more validation details.

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 clearly states it lists all sitemaps for a specific property with detailed information. This distinguishes it from siblings like 'get_sitemaps' (basic listing) and 'get_sitemap_details' (single sitemap). The verb 'list' and resource 'sitemaps' are specific.

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 explains how to use the site_url parameter (e.g., domain property covering subdomains) and mentions filtering by page. However, it does not provide explicit guidance on when to use this tool versus alternatives like 'get_sitemaps' or 'submit_sitemap'.

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