line_broadcast

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

No annotations are provided, so the description carries the full burden, and it omits the behaviors that matter most: that this is an irreversible mass delivery reaching every follower, that LINE enforces a broadcast quota/rate limits, and that a channel access token with the right scope is required. None of these are disclosed.

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 front-loaded sentence with no filler, and the recipient scope appears before the qualifier. It is efficient but borders on under-specification for a broadcast mutation.

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?

This is an outbound, irreversible, quota-limited mass-send operation with no annotations, no output schema, and 0% parameter documentation. For that complexity profile, the one-line description leaves out essentials an agent needs before calling: auth token handling, delivery scope, and irreversibility.

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%, so the description must compensate and does not. 'message' is inferable from the prose, but 'channel_access_token' is undocumented in both the schema and the description, leaving the agent no guidance on where it comes from or that it is effectively required.

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 states a specific verb (broadcast) and resource (a text message) plus scope (all followers of your LINE Official Account), which implicitly separates it from the sibling line_send_message/line_reply_message that target individuals. It is clear but never names those siblings, so 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?

Usage is only implied: 'broadcast ... to all followers' hints at mass delivery versus a 1:1 send, but there is no explicit when-to-use, when-not-to-use, or named alternative (line_send_message, line_send_flex_message, line_reply_message). An agent must reason about the distinction on its own.

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