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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: 'saved' signals this reads persisted data rather than performing a live probe, and 'unknown is not proof of healthy provider delivery' tells the agent how to interpret an inconclusive result. It stops short of stating freshness/staleness guarantees.

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 sentence with the purpose front-loaded and the interpretive caveat immediately after; no filler words and nothing redundant with the title or annotations.

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 and the annotations are rich, so return values and safety need no explanation. What is missing is the relationship to adjacent read tools and any notion of data freshness — exactly the gap that matters for a 'saved' health snapshot.

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 100% and both parameters (agent_id, channel_id) carry their own sourcing hints, so the schema does the work. The description adds nothing about either parameter, but the baseline of 3 is appropriate when coverage is complete.

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?

It says the tool 'Reports saved channel activity/health', which identifies the resource but leaves the verb ambiguous — 'reports' could mean a snapshot, a probe, or a summary. With siblings like line_activity_read, agent_channel_activity_read, line_connection_verify, and provider_status in the same family, the description does nothing to separate this tool's scope from theirs.

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 when-to-use statement and no alternative named — an agent cannot tell from this text whether to call line_health_read or line_connection_verify for a liveness question. The trailing caveat is an interpretation warning, not usage guidance.

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