wp_delete

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

No annotations exist, so the description must declare behavioral traits itself. It indicates deletion but doesn't explain whether the removal is permanent, what side effects occur on the WordPress installation, or any required permissions. The 'confirm: Required' note hints at a safety mechanism but isn't elaborated.

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 concise and front-loaded, stating the action in the first sentence and listing arguments without filler. The brevity is effective but omits important behavioral and usage context.

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?

For a destructive tool, the description is too minimal. It fails to define what a 'WordPress location' is, leaves the confirm parameter's semantics ambiguous, and doesn't mention effects or return values. The presence of an output schema doesn't make up for missing safety and usage details.

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 coverage is 0%, so the description must compensate. It restates location_id as 'Location id' and says confirm is required, but doesn't clarify what confirm does or how to set it. Furthermore, the schema marks confirm as optional with a default, so the description's claim that it is required creates potential confusion.

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 a specific action and resource: 'Remove a WordPress location from the manager.' This is clear and unambiguous, though it doesn't explicitly distinguish itself from sibling tools by naming alternatives.

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?

There is no guidance on when to use this tool versus alternatives. It simply says what it does, with no mention of wp_install, wp_get, or other related tools that might be confused with it.

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