wordpress_list_menu_items

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

With no annotations provided, the description carries the full burden. It partially compensates by disclosing return format ('hierarchical list', 'links and ordering'), but omits auth requirements, rate limits, caching behavior, and error handling.

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 efficiently two sentences with information front-loaded. Minor deduction for the '[UNIFIED]' metadata prefix which adds noise without value.

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 2-parameter read operation, the description adequately covers the return value (compensating for lack of output schema) but falls short on parameter documentation. Given zero schema descriptions, the lack of parameter semantics prevents a higher score.

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%, requiring the description to fully document both `site` and `menu_id`. While 'specific menu' implies `menu_id`, the `site` parameter is completely undocumented and neither parameter's format or constraints are explained.

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 tool 'List[s] all items in a specific menu' with specific verb and resource. It effectively distinguishes from sibling `wordpress_list_menus` by emphasizing 'items' and 'specific menu' (requiring a menu ID) versus listing menus themselves.

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?

While the implied usage is clear from the name and description, there is no explicit guidance on when to use this versus `wordpress_get_menu` (metadata) or `wordpress_create_menu_item`, nor are prerequisites (like needing a valid menu_id) stated.

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