wp_list_menu_items

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

With no annotations, the description must carry the behavioral burden; 'List' implies a read-only operation and 'in menu order' communicates default ordering. However, it does not disclose pagination, status filtering, or response format, which are material for a list operation with no output schema.

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 one short, front-loaded sentence with no filler; every word contributes to stating the core behavior. Its brevity contributes to under-specification, but as a structural choice it is efficient.

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 7 parameters, no annotations, and no output schema, yet the description gives no information about required inputs, filtering, pagination, or return shape. 'Classic' is left undefined and no relationship to sibling menu tools is provided, so an agent cannot reliably select or invoke the tool.

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 only 29%, so the description needed to compensate, but it explains none of the seven parameters. The phrase 'menu order' merely restates the schema's orderby default and adds no meaning beyond the structured input schema.

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 uses a specific verb ('List') and resource ('classic menu items'), and adds ordering context ('in menu order'). It is clear about what the tool does, but it does not explicitly differentiate itself from sibling tools like wp_list_menus or wp_get_menu_item.

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 guidance is given about when to use this tool instead of alternatives such as wp_list_menus, wp_get_menu_item, or wp_list_pages. There are no exclusions, prerequisites, or clarification of the 'classic' distinction.

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