wordpress_get_menu_items

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

No annotations provided, and the description only states 'Get menu items' without disclosing read-only nature, authentication requirements, or any side effects. It fails to compensate for the absence of annotations.

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 at one sentence, but it sacrifices necessary detail. It is front-loaded but lacks completeness, which is acceptable for conciseness but not for effectiveness.

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?

With no output schema and a misleading description, the tool definition is incomplete. It fails to explain how to specify a menu or what the output format is, leaving critical gaps for a simple read operation.

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?

Despite 0 parameters and 100% schema coverage, the description claims the tool can target a specific menu, yet provides no parameter for that. This contradiction adds confusion rather than value.

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 states it retrieves menu items from a specific menu or all menus, but the input schema has no parameters to specify a menu, making the 'specific menu' option misleading. It is not a tautology and distinguishes from siblings like get_menus, but the lack of parameters undermines clarity.

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 on when to use this tool versus sibling tools like wordpress_get_menus or wordpress_get_menu_locations. It does not mention prerequisites or alternatives, leaving the agent to infer usage.

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