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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful behavioral fact — statuses are derived from real on-chain activity rather than self-reported state — which helps an agent trust the output. However, it says nothing about refresh cadence, staleness of the underlying data, or what 'dormant' vs 'stale' actually mean operationally.

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 tight sentence with the resource front-loaded and the status vocabulary enumerated compactly. Nothing is wasted, though the dash-clause structure packs two ideas into one line and could be slightly clearer.

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 need not be explained, and the description adequately conveys what the tool reports. The gaps are the undocumented `limit` parameter and the absence of any routing guidance among ten sibling tools, which leaves it minimally viable rather than complete.

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% for the single `limit` parameter, and the description never mentions it. The only clue is the schema default of 100, so an agent gets no guidance on whether limit caps agents returned, pagination size, or something else.

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 a specific resource (agent liveness) and enumerates the exact classification vocabulary it returns: alive/dormant/stale/dead/unknown. It also grounds the classification in a data source (actual on-chain activity). It does not explicitly contrast itself with siblings like get_agent_sla or get_reputation_summary, so it stops short of a 5.

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?

There is no statement of when to reach for this tool versus check_wallet_reputation, get_agent_sla, or the other health-oriented siblings. The usage is only implied by the purpose statement, and no prerequisites, exclusions, or alternatives are offered.

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