Проверка связи

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds non-obvious context the annotations cannot: that this is an application-level health probe rather than the removed protocol `ping`, and that the name is a frozen public contract. That is genuine value beyond the schema.

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 core behavior ('returns pong') is front-loaded in the first clause. The remaining notes about the spec version and the fixed name are slightly meta and consume space an agent doesn't strictly need, but they serve a real purpose in preventing misuse of the name, so they largely earn their place.

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 trivial zero-parameter health check with a full output schema and rich annotations, the description supplies everything relevant: behavior, semantics of the name, and safety is covered structurally. Only the 'when to call me' trigger is left implicit, which is the one minor gap.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify, and it introduces no misleading parameter hints.

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 concrete behavior — a health check that returns 'pong' — and explicitly distinguishes itself from the protocol-level `ping`, which prevents an agent from mistaking it for a network diagnostic. What the tool does is unambiguous. It doesn't need to differentiate from siblings since none of the listed tools (crawl, fetch_page, web_search) are comparable.

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 identifies itself as an application health tool, which implies the use case (connectivity/liveness check), but it never states when an agent should call it — e.g. before a batch of operations, or to verify server availability. No alternatives or exclusions are named because none exist among the siblings.

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