Get WordPress User

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

Annotations already declare read-only/idempotent safe behavior. The description adds meaningful behavioral context: the 'edit' context requires admin and returns roles/capabilities, and the response_format parameter controls markdown vs. JSON output. This goes beyond what the schema provides.

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 concise and front-loaded with the purpose, followed by a structured Args/Returns layout. Every sentence earns its place with no redundancy or fluff.

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 simple get-by-id tool, it covers all parameters, enum options, and the return type (WPUserItem). It does not mention error behavior for missing IDs, but given the annotations and simple scope, this is not a critical gap.

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 coverage is 100%, so all parameters are already well-documented. The description repeats param details and adds a note about 'edit' requiring admin, but this is already in the schema, so the value added beyond structured data is minimal.

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 'Fetch a single user by ID' with a specific verb and resource. The 'single user' scope distinguishes it from sibling tools like wp_list_users (list), wp_update_user (update), and wp_delete_user (delete).

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?

It provides clear context for when to use the tool (when you have a user ID) and includes a usage note for the 'edit' context requiring admin. However, it does not explicitly mention alternatives like wp_list_users for listing users, though this is implied by the sibling set.

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