Delete LINE audience

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

The description adds that the action is irreversible and requires confirm=true, which goes beyond the annotations. The annotations already indicate destructiveHint=true and readOnlyHint=false, and the description confirms the destructive nature. It also discloses the return format {success, deleted_id}, adding behavioral context the annotations lack.

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 extremely concise: two sentences that front-load the key action and provide essential details without redundancy. Every word serves a purpose.

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?

For a simple deletion tool, the description adequately covers the purpose, required parameter source, confirm flag, and return format. No output schema exists, but the return snippet clarifies what to expect. The description is complete enough for an agent to use the tool 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?

With schema description coverage at 0%, the description must illuminate parameters. It explains audience_group_id (numeric, from line_list_audiences) and highlights the confirm parameter's necessity. However, the 'oa' parameter is left unexplained, and the description does not fully compensate for the missing schema descriptions.

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 starts with 'Delete an audience group', clearly stating the verb 'delete' and the resource 'audience group'. It distinguishes from sibling delete tools like line_delete_rich_menu by specifying 'audience'.

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 notes that confirm=true is required and that audience_group_id comes from line_list_audiences, providing clear usage context. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., line_update_audience), which would strengthen the guidance.

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