wordpress_get_menu_items

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

With no annotations, the description carries the full burden for behavioral disclosure. It indicates a read-only 'Get' operation with scope options, but does not disclose return structure, pagination, ordering, or whether menu items are hierarchical. It is not misleading but minimal.

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 sentence that is front-loaded and free of filler. It accurately captures the tool's purpose without wasted words.

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?

The tool is simple (no parameters, no output schema), and the description states what it returns (menu items) and the scope. However, it lacks details about the output format (e.g., fields, nesting), which would help an agent understand the response. Still, for such a straightforward retrieval, the description is largely adequate.

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 zero parameters, so per the rubric the baseline is 4. The description's mention of 'specific menu or all menus' adds conceptual scope but does not introduce parameter details since no parameters exist. This is not a contradiction, just a description of output variety.

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 uses a specific verb and resource: 'Get menu items', and explicitly states the scope ('from a specific menu or all menus'). This clearly distinguishes it from sibling tools like wordpress_get_menus, which retrieves menus themselves.

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 implies usage for retrieving menu items, but provides no explicit when-to-use or alternatives. It does not mention how it relates to wordpress_get_menus or menu item CRUD tools, leaving the agent to infer based on naming.

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