Manage LINE rich menu aliases (tab switching)

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

The description adds significant context beyond annotations: it explains the tab-switching mechanism, that delete only removes the alias not the menu, and that create/update require rich_menu_id. It also clarifies the non-idempotent nature (modify) and does not contradict any annotation.

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 well-structured with clear sections for modes, parameters, return values, and an example. It is slightly verbose but every sentence adds value. The use of Thai example is helpful but could be omitted for brevity.

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's complexity (4 parameters, 5 modes) and no output schema, the description fully covers the return format for each mode and provides a complete example. It leaves no major gaps for an AI agent to understand invocation and expected outcomes.

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 the description adds meaning by stating parameter rules (alias_id required except list, rich_menu_id required for create/update) and explaining the role of each mode. It also clarifies that 'oa' is optional and defaults to active OA.

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 manages rich menu aliases for tab-switching, with specific verb+resource (CRUD on aliases). It distinguishes from sibling tools by focusing on alias management rather than menu building or linking.

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 explains when to use each mode (create, update, delete, get, list) and specifies required parameters per mode. It provides practical guidelines but does not explicitly contrast with sibling tools for when-not-to-use.

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