wordpress_remove_capability

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

The description indicates a destructive action ('remove'), but no annotations are provided to clarify safety. It does not explain effects on users who have the capability via multiple roles, whether the action is reversible, or error conditions (e.g., removing non-existent capability).

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 6-word sentence, which is concise but lacks sufficient detail. It is technically efficient but borderline under-specified for a tool with no parameter descriptions.

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?

Despite being a simple tool with two parameters, the description fails to provide operational context such as typical usage flow (e.g., first get capabilities, then remove). It does not leverage the presence of sibling tools to guide the agent.

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?

With 0% schema description coverage, the description must compensate, but it does not describe the two required parameters ('role', 'capability') at all. The tool name implies 'capability' but no format or examples (e.g., role slug, capability key) are given.

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 'Remove capability from a user role' clearly states the action (remove) and the resource (capability from a role). It distinguishes itself from siblings like wordpress_add_capability and wordpress_get_capabilities.

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, such as checking if the capability exists first or understanding that it is the inverse of wordpress_add_capability. It lacks any context about prerequisites or typical use cases.

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