wordpress_create_role

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

With no annotations, the description carries full burden. It labels the tool as 'create', implying a mutation, but fails to disclose side effects (e.g., role conflict, default permissions, required user capabilities). This lack of detail hinders safe invocation.

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?

At five words, the description is extremely concise, but this brevity sacrifices necessary context. While it contains no wasted words, it omits structural elements (e.g., sections, examples) that would improve usability.

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 state-modifying tool with no output schema and no annotations, the description is incomplete. It fails to mention return values, error conditions, or required permissions, leaving significant gaps for an AI agent to operate safely.

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%, and the description adds no meaning beyond parameter names. It does not explain that 'role' is likely a slug (must be unique) or that 'displayName' is the human-readable label, leaving critical semantics unspecified.

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 action ('Create') and resource ('custom user role'), which distinguishes it from siblings like 'wordpress_assign_role' or 'wordpress_delete_role'. However, it lacks any explanation of what 'custom' entails or how it differs from built-in roles, leaving some 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?

No guidance is provided on when to use this tool versus alternatives such as 'wordpress_add_capability' (for modifying existing roles) or 'wordpress_assign_role' (for user assignment). An AI agent would need to 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.