wordpress_get_menus

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

With no annotations provided, the description must inform the agent about behavioral traits. It only states the basic function without mentioning side effects, permissions, or output details. The agent cannot determine if this is a read-only operation or requires special authentication.

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 extremely concise (4 words), which is efficient but lacks necessary detail. An appropriate size would include behavioral notes. The structure is minimal, with no front-loading of critical information.

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 the tool's simplicity (no parameters, no output schema), the description should compensate by explaining the return format or the meaning of 'navigation menus'. Without that, the agent may not know what to expect from the output. The description is insufficient for effective use.

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?

The tool has zero parameters, and schema coverage is 100%. However, the description adds no additional semantic meaning beyond the tool name and the word 'all'. It could have explained what constitutes a navigation menu or the scope of 'all' (e.g., across all sites in a network).

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 verb 'Get' and resource 'all navigation menus', which accurately reflects the tool's function. It distinguishes itself from siblings like wordpress_get_menu_items (which returns items within a menu) and wordpress_get_menu_locations (which returns assigned locations).

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it specify any prerequisites or exclusions. This is a critical gap given the large number of sibling tools.

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