Create a navigation menu

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

The description discloses that the menu is created empty and that locations can be assigned, which are behavioral details beyond the annotations. It does not mention return values or potential side effects beyond location assignment, but annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) are not contradicted, and the workflow hint adds value.

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 long, front-loaded with the main purpose, and includes the pointer to add_menu_item. Every phrase contributes to clarity, with no redundant or filler content.

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 5 parameters and no output schema, but the description covers the essential workflow: creating an empty menu and then adding items. It does not explicitly state the return value (e.g., menu ID), but the mention of adding entries afterwards implies that an identifier is produced for later use. Overall, it is sufficiently complete for an agent to use the tool correctly.

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 input schema already describes all 5 parameters with 100% coverage, so the description does not need to restate them. The mention of 'theme locations' mirrors the schema's 'locations' parameter, and the description adds no new parameter-specific guidance beyond what the schema provides.

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 action ('Create') and the resource ('empty navigation menu'), and explicitly says it optionally assigns to theme locations. It distinguishes itself from add_menu_item by noting that entries are added afterwards, making the tool's specific role unambiguous.

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?

It directly instructs the user to use add_menu_item for adding entries, naming the appropriate next step. The phrase 'optionally assigning it to one or more theme locations' clarifies when locations are relevant, and the overall context implies that this tool is for creating new menus rather than updating or deleting them.

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