mainwp_clients_delete

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

The description adds two behavioral traits: it is a Pro feature and requires confirmation. However, it does not disclose whether deletion is irreversible, what consequences it has (e.g., cascading effects), or any permission requirements. With no annotations, the description's transparency is basic but not comprehensive.

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, efficient sentence that immediately conveys the tool's purpose and key constraints. Every word earns its place; there is no redundancy or unnecessary detail.

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 action without an output schema or annotations, the description is too minimal. It omits critical context such as what happens after deletion (e.g., return value, irreversible nature), required permissions, and whether the action can be rolled back.

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 100%, so the parameters are already well-documented. The description does not add new meaning beyond what the schema provides, but it reiterates the confirmation requirement which aligns with the schema's description of the 'confirmed' field.

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 clearly states the tool deletes a client from MainWP, using a specific verb ('Delete') and resource ('client'). It distinguishes from sibling tools like mainwp_clients_add or mainwp_clients_get, as it is the only deletion operation for clients.

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 is provided on when to use this tool versus alternatives (e.g., archiving or suspending). It only mentions that confirmation is required, but does not specify conditions or when not to use it.

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