wordpress_get_menus

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

No annotations are provided, so the description carries the full burden. 'Get all navigation menus' implies a read-only operation, but it doesn't disclose behavioral traits like whether it requires authentication, returns paginated results, includes inactive menus, or provides error handling. The description is too minimal for a tool with no annotation coverage.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place.

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 annotations, no output schema, and a simple but incomplete description, the tool definition is inadequate. The description doesn't explain what 'all' entails (e.g., includes draft menus?), the return format, or error conditions. For a read operation with zero structured metadata, more context is needed.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate given the empty schema. A baseline of 4 is justified since there are no parameters to explain.

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 'Get all navigation menus' clearly states the verb ('Get') and resource ('navigation menus'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'wordpress_get_menu_items' or 'wordpress_get_menu_locations', which are related but distinct operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention whether this retrieves all menus at once, if there are filtering options, or how it differs from other menu-related tools like 'wordpress_get_menu_items' or 'wordpress_get_menu_locations'.

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