wordpress_delete_role

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't state whether this action is reversible, what permissions are required, what happens to users with this role after deletion, or if there are any confirmation prompts. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. No extraneous words or redundant information are present.

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 destructive nature, lack of annotations, no output schema, and a parameter with 0% schema coverage, the description is incomplete. It doesn't address critical context like behavioral risks, parameter details, or expected outcomes. For a mutation tool with these gaps, the description should do more to guide safe and correct usage.

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 schema has 1 parameter with 0% description coverage, meaning the parameter 'role' is undocumented in the schema. The description adds no semantic information about this parameter—it doesn't explain what 'role' refers to (e.g., role name string), valid values, or examples. The description fails to compensate for the low schema coverage.

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 custom user role' clearly states the action (delete) and the resource (custom user role). It distinguishes from siblings like 'wordpress_delete_user' or 'wordpress_remove_capability' by specifying the target is a role, not a user or capability. However, it doesn't explicitly differentiate from 'wordpress_get_roles' or 'wordpress_create_role' beyond the verb, so it's not a perfect 5.

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. It doesn't mention prerequisites (e.g., role must exist, must be custom), exclusions (e.g., cannot delete default roles like 'administrator'), or related tools like 'wordpress_get_roles' to check existing roles first. The agent must infer usage from the name alone.

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