wordpress_get_menu

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

With no annotations provided, the description carries the full burden. It adds valuable context that the tool returns a 'hierarchical structure' of items, indicating nested data format. However, it lacks explicit confirmation this is read-only, safe, or details about caching/rate limits.

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?

Two efficient sentences with the action front-loaded. The '[UNIFIED]' tag at the beginning is unnecessary metadata noise but doesn't significantly impact readability.

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?

Adequate for a simple read operation with no output schema. The mention of 'hierarchical structure' hints at return format. However, the complete lack of parameter documentation leaves critical gaps for an agent trying to construct valid inputs.

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 0% for both required parameters ('site' and 'menu_id'). The description fails to compensate by explaining whether 'site' expects a URL or ID, or what format 'menu_id' takes (WordPress term_id vs location slug).

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 retrieves detailed information about a specific WordPress menu including all items, distinguishing it from wordpress_list_menus (which lists all menus) and wordpress_create_menu. The '[UNIFIED]' prefix is noise but doesn't obscure the clear verb-resource combination.

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 provided on when to use this versus wordpress_list_menu_items or wordpress_list_menus. Does not mention that menu_id must be obtained from list_menus first, or prerequisites like site authentication.

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