create_conditional_menu

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

The annotations already indicate a mutating operation (readOnlyHint: false), and the description adds no extra behavioral context beyond simply stating creation. It does not mention whether an existing conditional menu is overwritten, whether replacement occurs, or any side effects.

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 short, only six Chinese characters, but this is under-specification rather than effective conciseness. It lacks any structural information about conditions, button layout, or matching rules.

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 nested object parameters, an output schema, and a family of related menu tools, this description provides almost no useful context. The agent cannot determine the format of match_rule, the constraints on buttons, or how this conditional menu interacts with the standard menu.

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 0%, and both parameters (buttons and match_rule) are open objects with no documented properties. The description does not explain what these parameters should contain or how they relate to 'personalized menu', leaving the agent with no guidance for constructing valid arguments.

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 states a specific verb and resource: '创建个性化菜单' (create personalized menu). However, it is vague about what makes it 'conditional' and does not differentiate it from the sibling tool create_menu, which also creates a 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?

There is no guidance on when to use this tool versus alternatives like create_menu or try_match_conditional_menu. The description provides no context about when conditional menus are appropriate or how they differ from regular menus.

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