wordpress_get_roles

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. While 'Get all' implies a read-only operation, it doesn't specify whether this requires authentication, what format the roles are returned in (e.g., array of role objects with capabilities), or if there are any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple, parameterless tool.

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 simplicity (no parameters, no output schema), the description is minimally adequate. However, with no annotations and no output schema, it lacks details about the return format (e.g., what data structure contains the roles) and behavioral context. For a read operation, this is acceptable but leaves room for improvement in clarifying what 'all WordPress user roles' entails.

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 tool has zero parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain any parameters, which is appropriate. A baseline of 4 is given since no parameter information is required beyond what's already covered by the empty schema.

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 'Get all WordPress user roles' clearly states the action (get) and resource (WordPress user roles). It's specific enough to understand the tool's function, though it doesn't explicitly differentiate from similar sibling tools like 'wordpress_get_capabilities' or 'wordpress_get_users' which might return related but different data.

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. With many sibling tools available (e.g., 'wordpress_get_capabilities', 'wordpress_get_users'), there's no indication of when this specific role-fetching tool is appropriate or what distinguishes it from other user/role-related tools.

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