Get LINE message engagement stats

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context beyond annotations: data lag, privacy thresholds, broadcast type restrictions, and the shape of the return object. No contradiction with annotations.

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?

The description is succinct, with two paragraphs. The first sentence states the core purpose, and the second paragraph adds caveats. Every sentence is informative with no fluff.

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?

Given the tool has 3 params, no output schema, and annotations indicate safe read-only operation, the description covers all necessary aspects: what it does, the return object structure, important caveats (lag, privacy, broadcast types). It is complete for an agent to decide and invoke correctly.

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 low (33%), but the description reinforces the meaning of request_id and its broadcast type requirement. It does not explain oa or response_format beyond what schema provides. Overall, the description adds moderate value to param understanding, but could be more explicit about optional parameters.

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 clearly states it fetches per-broadcast engagement stats for a request_id, listing specific metrics (impressions, opens, clicks, CTR, per-URL click breakdown). It distinguishes from siblings by specifying it's for a prior line_send_message, which is unique among the listed LINE tools.

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 description provides explicit caveats: ~24h data lag, stats stable at T+1; returns null for privacy below ~20 users; only for narrowcast/multicast/broadcast. It also directs to use request_id from a prior line_send_message. This gives clear when-to-use and when-not-to-use context.

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