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

Annotations already cover safety, but the description adds real substance: ~270 probes per agent over 30 days at a 15-minute cycle, an explicit contrast with one-shot URL pings, a $0.01 cost, and the REST path. It also previews the output fields (uptime, p50/p95, flaps, last-probe age), which is more behavioral context than most read-only tools supply.

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 core question and verdict vocabulary, then cost/provenance, then a compact argument list. Some marketing framing ("before your agent wastes timeouts calling a dead service", "not a one-shot ping like generic URL checkers") is persuasive padding, though it does convey the probe-depth differentiator.

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 don't need spelling out, and the description still names the key fields; parameters and cost are both covered. The only shortfall is routing ambiguity against get_agent_liveness and get_agent_sla, which the description does nothing to resolve.

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 0%, so the description carries the burden and mostly does: it explains agent_id is an ERC-8004 id, that solana_asset is the alternative identifier, and that window_days is an SLA window bounded 1-30 with default 7 — a constraint the schema does not encode. It doesn't state that the parameters are optional or how the two identifier params interact if both are supplied.

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?

Specific verb and resource: it answers whether an agent endpoint is currently alive and returns a named verdict (ALIVE/DEGRADED/DOWN/UNKNOWN). That is far more precise than a tautology. However, it never distinguishes itself from the near-identically named sibling get_agent_liveness or from get_agent_sla, so an agent must guess which of the three to call.

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?

"Call it before calling an unknown agent's endpoint" gives a concrete trigger, and the pre-flight framing implies the exclusion (known/healthy agents don't need it). It stops short of naming alternatives, so the overlap with get_agent_liveness and get_agent_sla is left unresolved.

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