wordpress_list_menu_items

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

The description implies a read operation with 'List' but does not explicitly state that it is non-destructive. With no annotations, the description carries the full burden; it is adequate but lacks explicit safety or limitation information.

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 concise (one sentence) but includes a '[UNIFIED]' prefix that may be extraneous. It is front-loaded and wastes few words, though the prefix could be removed for clarity.

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 no output schema and no annotations, the description provides basic functionality and return format but does not differentiate from siblings like wordpress_get_menu. It is minimally complete but lacks context for an agent to make informed choices.

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 coverage is 0%, so the description must compensate. It only indirectly explains menu_id (the specific menu) but does not describe the 'site' parameter at all. This leaves a significant gap for correct invocation.

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 'List all items in a specific menu' and specifies the output format as 'hierarchical list of menu items with links and ordering.' This distinguishes it from sibling tools like wordpress_list_menus and wordpress_get_menu.

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 on when to use this tool versus alternatives. The description does not mention prerequisites or conditions for use, leaving the agent to infer from the tool name and siblings.

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