get-sitemaps

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds behavioral scope beyond annotations by clarifying that results include 'every sitemap Yandex knows ... including ones it discovered,' which is useful context for interpreting the data. It does not mention pagination, rate limits, or return format, so it is not fully complete.

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?

Three sentences, zero waste. The core purpose is front-loaded, followed by positive usage guidance and then precise exclusions with named alternatives.

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 read-only list tool with rich annotations and no output schema, the description covers purpose, usage, and sibling routing well. The main gap is the undocumented limit parameter, but an agent can still invoke the tool correctly with the required host_id.

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 50%: host_id has only a minimal 'Host ID' description, and limit is undocumented. The description implies the host parameter but adds no meaning for limit (e.g., maximum 100, behavior), leaving a required parameter inadequately explained.

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 states a specific verb and resource: 'List all sitemaps for a host.' It further distinguishes itself from sibling tools get-user-sitemaps and add-sitemap by explicitly naming them and describing scope including discovered sitemaps.

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?

It gives explicit when-to-use criteria ('Use when the user wants every sitemap Yandex knows ... including ones it discovered') and explicit when-not-to-use alternatives ('Do not use it for only the files the user uploaded; call get-user-sitemaps. Do not use it to add a file; call add-sitemap.').

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