Menus: add item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write-but-safe profile is covered. The description adds nothing beyond that: no duplicate-name handling, no ordering/position semantics, no note that parent requires an existing item.

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?

A single six-word sentence with no filler and the action front-loaded. It is efficient, though its brevity borders on under-specification for a five-parameter mutation.

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?

With a fully documented schema and annotations covering the safety profile, the definition is minimally viable. It still omits mutation-relevant context such as what happens on duplicate items or how nested parent items are validated.

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 icon, name, entity, parent, and menu_id are all documented in the schema itself. The description only echoes 'entity' and adds no format, defaulting, or nesting details 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?

States a clear verb+resource ('Add a menu item') and scopes it to an entity, which is one of the required parameters. It does not differentiate from the only closely related sibling (menus_list), but the purpose itself is 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?

There is no when-to-use guidance, no mention of prerequisites (e.g. menu_id must already exist), and no reference to alternatives. The agent must infer that this is the creation counterpart to menus_list.

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