list_sitemaps_tool

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It does not state that this is a read-only operation, mention any output format, or note potential side effects. The word 'list' implies a query, but the description lacks explicit transparency about behavior.

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 a single, front-loaded sentence with zero wasted words. It fully conveys the action and object in one concise statement.

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 simple list tool with one parameter, the description is complete in conveying what it does and that it requires site_url. An output schema exists, reducing the need to explain return values. However, the absence of usage guidelines and behavioral notes prevents a perfect score.

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 coverage is 100% with site_url described as 'Site URL or domain property.' The description adds only 'for a site,' which loosely links to the parameter but does not provide additional meaning, format, or usage details beyond the schema. Baseline 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 uses a specific verb ('list') and resource ('all sitemaps') with an explicit scope ('for a site'), clearly distinguishing it from sibling tools like get_sitemap (single sitemap), submit_sitemap, and delete_sitemap. It names the exact action and object.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_sitemap to retrieve a specific sitemap or submit_sitemap to add one. The description simply states the action without context or exclusions.

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