wordpress_list_menus

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

No annotations provided, so description carries full burden. It discloses return structure (menus with locations and item counts) which substitutes for missing output schema. However, lacks disclosure on read-only safety, caching behavior, rate limits, or pagination. 'List' implies read operation but this is not explicit.

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 no redundant filler. Front-loaded purpose statement followed by return value disclosure. Minor deduction for '[UNIFIED]' prefix which appears to be metadata noise rather than descriptive 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?

Partially complete. Compensates for missing output schema by describing return values (locations, item counts). However, fails to document the required 'site' parameter (0% schema coverage). Adequate for simple list operation but missing critical param semantics.

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% with one required parameter ('site'). The description fails to compensate by explaining what the site parameter represents (URL, ID, slug?), its format, or constraints. This leaves the parameter completely undocumented beyond the schema name.

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?

Specific verb 'List' + resource 'WordPress navigation menus' with scope 'all'. The 'Returns list of menus with their locations and item counts' clarifies output shape. 'List all' clearly distinguishes from sibling wordpress_get_menu (singular) and wordpress_list_menu_items (different resource).

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 when-to-use or alternative guidance provided. However, the scope word 'all' implicitly signals this is for bulk enumeration versus retrieving a specific menu (wordpress_get_menu). No prerequisites or error conditions mentioned.

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