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 without the description. The one genuine addition is that the payload excludes customer bodies and provider payloads, which prevents an agent from selecting this tool expecting message content. Nothing is said about pagination, cursors, or how far back 'recent' reaches.

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 no filler, front-loaded with the verb and the returned fields, and the exclusion clause placed where it does the most work. Nothing could be removed without losing information.

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?

With rich annotations, a fully described schema, and an output schema to explain return shape, the description covers what remains: purpose and content scope. The gap is the absence of routing guidance against the many overlapping LINE read tools, which matters given this crowded sibling set.

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%, with limit, agent_id and channel_id all documented including the maximum and default. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 gives a specific verb ('Lists') and a precise resource ('recent event IDs/types/timestamps'), so an agent knows it returns event metadata rather than message content. It never names the near-neighbour tools (line_activity_read, line_health_read, line_profile_read), so sibling differentiation is left to inference.

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 use this tool versus line_activity_read or line_health_read, nor any prerequisites or exclusions. The purpose implies an auditing/monitoring use case, but the agent must guess at the selection criteria among several closely related read tools.

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