wordpress_delete_category

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

There are no annotations, so the description must fully disclose behavior. It merely says 'Delete a category' and omits critical behavioral details such as whether deletion is permanent, whether the 'force' parameter is required for non-empty categories, or what happens to associated posts. This leaves the agent without vital safety information.

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 short, containing only three words. While it has no wasted words, the extreme brevity is under-specification rather than efficient structure. There is no sentence structure or logical flow to guide the agent.

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 potential side effects (deleting a category), the description is drastically incomplete. There is no output schema, no annotations, and no explanation of the return value, error conditions, or impact on content. This is inadequate for a mutation tool.

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?

Schema description coverage is 0%, and the description does not mention either parameter. The schema only provides types (number, boolean) but no meaning for categoryId or force. The description offers no insight into how these parameters affect the deletion.

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 category' directly states the tool's action and target resource. However, it essentially restates the tool name 'wordpress_delete_category' without adding any additional information, such as scope, conditions, or side effects. This is a tautological restatement, so it only clarifies the obvious.

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 like wordpress_update_category or wordpress_get_categories. There are no prerequisites, exclusions, or references to related operations. The agent receives no context for tool selection.

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