wp_get_user

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

Explicitly declares read-only behavior and states auth requirements. With no annotations, this covers the key side-effect and access constraints, though it doesn't mention failure/not-found behavior.

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?

Every sentence adds useful information and there is no redundancy. The description is compact and front-loaded with the core action.

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?

Missing parameter semantics for install and no output schema or error behavior are provided. While the read-only nature and returned fields are mentioned, the call cannot be made confidently without knowing what 'install' refers to.

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 has no parameter descriptions, and the text only explains where user_id comes from. The 'install' parameter is never described, so the agent cannot fully understand how to fill both required arguments.

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?

States exactly what the tool does: reads one WordPress user by id, and lists the fields returned. Clearly distinct from sibling list/create/update/delete user tools.

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?

Provides practical context: read-only, obtains user_id from wp_list_users, and requires REST transport with an administrator app password. Doesn't explicitly contrast with alternative single-user lookup tools, but the prerequisites and source of user_id give enough direction.

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