wordpress_remove_capability

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., affecting all users with the role), reversibility, permission requirements, or return values. It only restates the action, adding little beyond the tool name.

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?

A single, succinct sentence that earns its place. It is not padded or vague; every word conveys essential meaning. This is an example of appropriate brevity, not 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?

The tool has two required parameters, no annotations, and no output schema. The description is adequate for a human but incomplete for an agent: it does not state what the tool returns on success/failure, whether the role or capability must already exist, or if the action is destructive. Contextual completeness is low.

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 description coverage is 0%, so the description must compensate. It mentions 'role' and 'capability' but adds minimal meaning beyond the property names. It clarifies that role is a user role, but gives no format, valid values, or how WordPress expects them.

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 a specific verb and resource: 'Remove capability from a user role'. It clearly distinguishes from sibling tools like wordpress_add_capability and wordpress_assign_role by naming the action and target. No ambiguity.

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 states what the tool does but offers no guidance on when to use it over alternatives, prerequisites, or context. There is no explicit 'when to use' or 'instead of' mention. Usage is only implied by the name and verb.

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