Build LINE Rich Menu (single panel)

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

Annotations indicate a mutation tool (readOnlyHint=false, destructiveHint=false). The description adds context: it mentions the internal workflow (validate → create → upload image → set as default), the critical domain switch for image upload, and constraints like image requirements and the 1,000-menu limit. 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 a single paragraph with clear front-loading of purpose. Each sentence contributes useful information, though it could be slightly more structured (e.g., bullet points for constraints). No wasted words.

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?

Returns values are specified ({ rich_menu_id, name, set_as_default, warnings[] }) despite no output schema. Constraints (image size, aspect ratio, file size) and limits (max 1,000 menus per OA) are provided. Input parameters are covered by the schema, but the description adds operational context.

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 88%, so the schema already documents most parameters. The description adds minor detail (e.g., 'must fit inside the image bounds' for areas) but largely restates schema info (image_url constraints, size dimensions). Baseline 3 is appropriate.

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 'Create' and the resource 'LINE Rich Menu', distinguishing it from the sibling tool line_design_rich_menu_image which renders images from labels. The title also specifies 'single panel' for precise 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 explicitly tells when to use ('single-panel menus only') and when not to, directing users to line_design_rich_menu_image for alternate image generation. It also explains the advantage of collapsing 4 API calls.

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