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

Adds substantial context beyond the annotations: it is a mutation that queues real work on a live third-party account and consumes that account's daily recrawl quota, it requires YANDEX_WEBMASTER_OAUTH_TOKEN, and it enumerates the two ok:false shapes (not_configured, no_matching_host) plus the cases that surface as hard errors (already queued, quota spent). Annotations (readOnlyHint=false, idempotentHint=false) are consistent with and enriched by this.

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?

Front-loaded with the action, then cost, then side effects, then failure modes — a sensible priority order with no filler sentences. It is dense and runs long for a two-parameter tool, which keeps it just below the top mark.

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, the description supplies the failure-response contract itself (ok:false reasons, and which failures raise errors instead), plus auth and quota prerequisites. Nothing an agent needs to call or interpret this tool 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%, so the baseline is 3; the description adds meaning by constraining url to a host that must be verified-matched on the account, which the schema does not say. The projectId scoping instruction is already in the schema, so it earns partial rather than full credit.

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?

States a specific verb+resource+scope: 're-crawl one specific URL on a project's matched host' via Yandex Webmaster. It explicitly distinguishes itself from the read-only sibling get_yandex_site_overview and from the general crawl-submission family by naming the exact upstream system.

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?

Gives clear usage context: BYO-token requirement, cost profile (FREE, no credits), and the quota/account consequences that gate a call. It stops short of naming alternatives for the same job (submit_indexnow, submit_bing_content, submit_baidu_urls) or stating an explicit 'don't use if...' condition, so it is clear but not fully routing.

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