yandex_site_summary

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

No annotations are provided, so the description carries the full behavioral burden. It lists output metrics but does not explicitly state that the operation is read-only, whether authentication is required, or whether there are rate limits. The read-only nature is strongly implied but not 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 short and front-loaded with the key metrics returned, followed immediately by the parameter format. There is no filler; every sentence adds useful information.

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 that an output schema exists and the tool has only one documented parameter, the description is largely sufficient for correct invocation. The main gap is the absence of usage context versus sibling tools, but that is addressed in the usage dimension.

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?

With 0% schema description coverage, the description compensates well by explaining that the single required site parameter accepts either a URL (https://example.com/) or a Yandex host id (https:example.com:443), including concrete examples.

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 identifies the resource and the metrics returned: SQI, pages in search, excluded pages, and problem counts for a Yandex site. It is a specific summary capability, but it does not explicitly differentiate itself from siblings like yandex_url_info or yandex_crawl_issues.

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 states what the tool returns and how to format the site parameter, but gives no guidance on when to use it instead of alternatives such as yandex_url_info, yandex_list_sites, or yandex_crawl_issues. It also provides no prerequisites or exclusions.

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