wp_get_user

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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys a read operation but does not explain what 'detailed information' includes, whether special permissions are needed, or how errors are handled. The description adds little beyond the retrieval intent.

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 with no filler. It front-loads the action and resource, making it immediately scannable and appropriately sized for a tool with one simple parameter.

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?

The single parameter is fully covered by the schema, and the description is minimally sufficient for a low-complexity read tool. However, there is no output schema and no annotation, so the vague phrase 'detailed information' leaves the response shape and behavioral edge cases unstated.

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 100%, so the schema already fully documents the 'id' parameter. The description's 'by ID' phrasing merely reinforces the schema and adds no new constraints, format details, or semantic distinctions.

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'), resource ('WordPress user'), and selection criterion ('by ID'). It clearly distinguishes this from sibling tools like wp_list_users or wp_update_user by indicating it targets a single known 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?

There is no explicit guidance on when to use this tool versus alternatives such as wp_list_users or wp_get_comment. The only implied usage is that you need a user ID, but no conditions, exclusions, or alternative tool references are provided.

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