Broadcast Text Message

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

Annotations already indicate destructiveHint: true. The description adds meaningful context by explicitly stating the broadcast scope ('to all users who have followed your LINE Official Account') and the warning about sending to all users. This complements the annotation without contradiction.

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?

Two sentences, each serving a distinct purpose: action definition and behavioral warning. No unnecessary words. Front-loaded with the core action.

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?

Despite lacking output schema, the tool is simple. The description fully covers what the tool does (broadcast text), how (plain text), and the scope (all followers). No missing critical information.

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. It clarifies that the message is 'plain text' and 'without formatting', adding semantic value beyond the schema's 'const: text' and string constraints.

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 the verb 'Broadcast' and the resource 'simple text message via LINE to all users who have followed your LINE Official Account'. It distinguishes from siblings 'broadcast_flex_message' and 'push_text_message' by specifying plain text and broadcast scope.

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 says 'Use this for sending plain text messages without formatting' which implies when to use. It also warns 'this message will be sent to all users', but does not explicitly state when not to use or contrast with alternatives like push_text_message for specific users.

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