ads_ping

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this measures round-trip time and relates to router/route/network health, but says nothing about blocking behavior, timeouts, how count affects duration, or rate limits.

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 compact sentence with no padding, front-loaded on the tool's subject. Slightly awkward phrasing ('statistics to the target') costs it the top score.

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?

An output schema exists, so return values needn't be explained, and annotations cover safety. Still missing are parameter meaning (port/count) and any usage guidance, which are needed for correct invocation even on a simple two-parameter tool.

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 0% and the description never explains the two parameters. It implies repeated measurement (count) and a target port, but neither is stated or given format/semantics, so it fails to compensate for the empty schema descriptions.

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 names the resource (ADS target) and the measurement (round-trip time statistics), plus the diagnostic domain (router/route/network health). However, it uses no explicit verb and reads more like a description of the output than of an action, so it is only vaguely distinguishable from siblings like ads_status or ads_routes.

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 parenthetical hints at a diagnostic use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many ads_* siblings. The agent is left to infer that this is a connectivity/latency probe.

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