wordpress_delete_role

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

There are no annotations, and the description doesn't disclose behavioral traits such as irreversibility, whether built-in roles can be deleted, or what happens if the role is assigned to users. It only states the action without side effects or limitations.

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 of six words, front-loaded with the action, and contains no filler. It is appropriately sized for a simple tool, though other dimensions suffer from under-specification.

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?

While the tool is simple, the description lacks essential context for a destructive operation: no mention of permanence, error conditions, or restrictions on which roles can be deleted. Given no annotations or output schema, this leaves the agent undersupplied.

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 a single 'role' string parameter with no description. The description doesn't explain what value 'role' expects (e.g., slug, name, ID) or how it relates to the 'custom user role' resource. With 0% schema coverage, the description fails to compensate.

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 the specific verb 'Delete' and identifies the resource as 'custom user role', which clearly distinguishes it from sibling tools like wordpress_create_role and wordpress_assign_role. The qualifier 'custom' adds specificity about the target role type.

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 usage guidance is provided. It doesn't mention when to use this tool, prerequisites, or alternatives such as wordpress_get_roles or wordpress_remove_capability. The context of when to delete a custom role is absent.

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