createMenu

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

The description reveals that the tool writes live data (consistent with annotations), lacks uniqueness enforcement on menu_name, and that duplicates cause rendering issues. It also warns against paginating unfiltered lists, adding behavioral context beyond what annotations provide.

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 sections and front-loaded essential information. It is slightly verbose due to the pre-check details, but each sentence adds value. Could be tightened without losing clarity.

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 description covers purpose, usage, preconditions, parameter interactions, and sibling links. However, it lacks full parameter documentation and does not explicitly state the return value structure (though implied). For a 9-param tool with no output schema, it is fairly complete but not exhaustive.

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?

The description explains menu_name, menu_title, and menu_active with semantics and constraints, but ignores 6 other parameters (menu_location, menu_div_id, etc.) despite 0% schema coverage. It partially compensates but leaves significant gaps.

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 menu - Create a new menu record' with a specific verb and resource. It distinguishes itself from siblings like createMenuItem and updateMenu by explicitly mentioning the workflow and alternatives.

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 includes a 'Use when' section, a required pre-check for duplicates with a specific server-side filter-find technique, and a 'See also' pointing to updateMenu. It also notes the consequence of duplicates, providing comprehensive when-to-use and when-not-to-use guidance.

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