wp_get_user

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

With no annotations, the description's 'Get' conveys a read-only, non-destructive operation, which is the key behavioral trait. However, it does not disclose response shape, permissions, error behavior, or any additional side effects.

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 front-loaded sentence with no filler. Every word contributes to identifying the tool's purpose.

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 getter with one required parameter, the description is minimally viable: an agent can call it with the required id. But the lack of explanation for include_email and the absence of any output context leave notable gaps.

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, but it only explains that 'id' identifies the user. The 'include_email' boolean parameter is left completely unexplained, leaving the agent unsure what toggling it does.

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 states a specific verb ('Get'), a resource ('WordPress user'), and the access method ('by ID'). This clearly distinguishes it from sibling tools like wp_list_users or wp_create_user.

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 phrase 'by ID' implies this tool should be used when retrieving a single known user, but it never explicitly names alternatives or says when not to use it. Guidance is present only by implication.

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