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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds the verification prerequisite, which is real value, but it says nothing about behavior on an already-submitted sitemap, quota/rate limits, or whether submission triggers a crawl.

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?

A single sentence with zero filler, and the key scoping constraint ('verified site') is placed where the agent will read it. Nothing is redundant with the title.

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 two-parameter submission tool with full schema documentation, annotations, and no output schema, the description covers the core operation and its main precondition. Minor gaps remain around duplicate-submission behavior, but nothing critical to calling it correctly is missing.

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% and the schema itself explains both fields, including the hostId format with a reference to yandex_list_sites. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ('Add a sitemap') and scopes it to 'Yandex Webmaster', which distinguishes it from gsc_submit_sitemap and bing_submit_sitemap by naming the platform. It stops short of explicitly contrasting with those siblings, but the vendor framing is enough for an agent to route correctly.

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 phrase 'for a verified site' implies a prerequisite, which is useful context, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., use yandex_list_sitemaps first to check existing entries). Usage is implied rather than stated.

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