List LINE Rich Menus

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

Annotations already provide readOnlyHint, destructiveHint, etc. The description adds context about the 1,000-menu limit and cleanup suggestion, plus details on the return structure. No contradictions with 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?

The description is well-structured with clear sections: purpose, limit info, args, returns, and usage tip. It is concise with no wasted words, earning its place.

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 read-only tool with 2 parameters, the description covers key aspects: purpose, limit context, parameter meanings, return structure, and usage advice. It lacks explanation of is_default vs is_selected, but overall it is adequate.

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 0%, so the description must compensate. It lists both parameters with brief explanations (e.g., 'optional OA id' for oa, and enum values for response_format). This adds some meaning but is minimal and only restates the schema with slight elaboration.

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 begins with a specific verb 'List' and resource 'rich menus' and adds the distinct feature of identifying the account-wide default. It clearly distinguishes from sibling tools like line_delete_rich_menu and line_build_rich_menu.

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 explicitly instructs to use this tool before line_build_rich_menu to avoid hitting the 1,000-menu cap, and references line_delete_rich_menu for cleanup. However, it does not specify when not to use it or other alternatives.

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