wordpress_delete_menu_item

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

While 'delete' implies a destructive action, the description provides no additional behavioral context such as irreversibility, permission requirements, or side effects. With no annotations, the description should disclose more about the tool's behavior.

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) but at the expense of informativeness. It fails to provide any value beyond restating the tool name, making it too brief for effective tool selection.

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 output schema, no annotations, and minimal description, the tool lacks essential context. Return values, side effects, error conditions, and parameter semantics are all missing, leaving the agent uninformed.

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 description does not mention the two parameters (itemId and force) at all. Schema coverage is 0%, so the description should explain these parameters, especially the 'force' boolean which is non-obvious.

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 'Delete a menu item' clearly specifies the action (delete) and the resource (menu item). It distinguishes from sibling tools like create, update, or get menu items, but it is minimal and could be more precise.

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 vs. alternatives (e.g., update_menu_item or bulk deletion). No mention of prerequisites or contexts where deletion is appropriate or not.

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