create_custom_menu

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

Annotations already provide destructiveHint=true and openWorldHint=true, so the bar is lower. The description adds context about template usage but does not elaborate on behavioral details such as whether an existing menu with the same name is overwritten or what permissions are needed. It does not contradict 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 two sentences, front-loaded with the action and key guidance. Every sentence earns its place; there is no filler or redundancy.

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?

The tool has 19 parameters with complex conditional relationships (e.g., many parameters matter only for specific templates). The description does not guide the agent on which parameters to set for each template type, nor does it describe the return value (no output schema). Given the complexity, the description is insufficiently complete.

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 100%, so baseline is 3. The description adds value by reinforcing that 'no content needed with templates,' which relates the 'content' parameter to template usage. This helps the agent understand parameter interdependencies beyond the schema.

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 'Create a custom menu page' and provides specific guidance on using templates (gauge/line_chart/gauge_and_chart/multi_chart). It distinguishes this creation tool from siblings like update_custom_menu and the various chart tools by focusing on creation and template usage.

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 recommends using templates when possible and notes that no content is needed with templates, giving clear context for when to use which parameters. However, it does not explicitly state when to use this tool versus alternatives like update_custom_menu or when not to use this tool.

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