Update LINE Audience

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

Discloses return structure per mode, example usage, and that LINE will reject non-upload audience mutations. Annotations already indicate mutation (readOnlyHint=false) and no destructiveness, so description adds context beyond 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?

Well-structured with two paragraphs and example. Front-loaded with main purpose. Every sentence is informative, though example could be slightly more compact.

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 no output schema, description specifies return types per mode. Covers behavioral nuances (read-only audiences) and provides example. Sufficient for agent to 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 100%, but description adds value by linking audience_group_id to line_list_audiences, explaining required parameters per mode, and providing an example that clarifies usage patterns.

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?

Explicitly states 'mutate an existing LINE audience group' with two specific modes. Distinguishes from sibling tools like line_list_audiences and line_delete_audience by focusing on mutation rather than listing or deletion.

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?

Provides clear when and when-not to use: only for Messaging-API-created upload audiences; audiences from OA Manager UI are read-only. Also tells where to get the audience_group_id (from line_list_audiences).

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