wordpress_check_user_capability

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

No annotations are present, so the description must communicate behavioral traits. However, it only states 'Check if user has specific capability' without disclosing return type (likely boolean), error handling (e.g., user not found), or that it is read-only. The agent lacks critical behavioral information.

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 sentence, which is concise. However, it is too brief and lacks detail. While it saves words, it does not earn its place by providing sufficient value. A slightly longer description with key details would be more useful.

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 no output schema and the need for return value disclosure, the description is incomplete. The agent cannot determine what the tool returns (e.g., boolean, string). Additionally, the tool lacks context among many similar sibling tools. The description fails to fully equip the agent for correct invocation.

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 input schema has 0% description coverage, meaning no parameter descriptions are provided. The tool's description also adds no explanation beyond the parameter names 'userId' and 'capability', which are self-explanatory but insufficient. The agent would benefit from knowing expected formats or constraints.

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 'Check if user has specific capability' clearly indicates the verb (check) and resource (user capability). It distinguishes from sibling tools like add_capability, remove_capability, and get_capabilities by implying a single capability check, though it doesn't explicitly differentiate from get_capabilities which lists all. Still, the purpose is clear.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like wordpress_get_capabilities for listing all capabilities, or wordpress_add_capability for modifying. Without such context, the agent may misuse the tool.

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