Hole Menü-Items

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

No annotations are provided, so the description carries the full transparency burden. It indicates a read operation ('Holt') and notes hierarchical output, but it does not disclose return fields, ordering, or whether all item statuses are included.

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 a single concise sentence, front-loaded with the action and resource, with no filler or redundant 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?

For a simple getter with one parameter and no output schema, the description sufficiently conveys the purpose and return shape (all items with hierarchy). It lacks minor details like output fields or error behavior, but is otherwise adequate.

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% since menuId has a description ('Menü ID'), so the schema fully documents the parameter. The description adds no extra parameter semantics, meriting the baseline of 3.

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 ('Holt'), the resource ('alle Items eines Navigationsmenüs'), and the specific scope ('mit Hierarchie'), distinguishing it from sibling tools like nav_list_menus which list menus rather than menu items.

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?

No explicit usage guidance or alternatives are provided. The description implies this tool is for retrieving hierarchical menu items, but it does not state when to prefer it over nav_list_menus or other navigation-related tools.

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