Menu Create

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

No annotations are provided, so the description carries the full behavioral burden. 'Create a new menu' implies mutation but says nothing about permissions required, what happens on duplicate menu_id, whether the menu is a Drupal menu entity, or any side effects — a significant gap for a write operation.

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 single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficiency. Every word earns its place, yet there is far too little of it for a four-parameter mutation tool.

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 four parameters at 0% schema coverage and no annotations, the description should explain the required fields and the nature of a 'menu' in this context. An output schema exists, so return values need not be described, but the input-side gap is severe.

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% across four parameters (menu_id, label, langcode, description), and the description adds no meaning for any of them. The agent cannot tell from either the schema or the description what 'menu_id' should look like or how 'label' relates to it.

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 a new menu'), which is clear enough for an agent to understand the operation. However, it offers no differentiation from siblings like menu_create's nearest neighbours (menu_link_create) or from generic create tools in the list, so the agent must rely on the name alone to disambiguate.

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 menu_link_create, module_create, or other create endpoints, and no prerequisites or context are given. The agent is left to infer usage from the tool name.

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