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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the sentence 'its server marks it read-only, so it runs straight away' merely restates the annotation. It adds no substantive context such as permission/auth requirements, behavior when unauthenticated, or response shape (no output schema exists to cover that gap).

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 purpose is front-loaded in the first sentence, which is good. But the third sentence ('Through Royally: its server marks it read-only, so it runs straight away') is awkwardly worded vendor framing that duplicates the annotations and does not earn its place.

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 two-parameter read tool with rich annotations and full schema coverage, the description covers purpose and default behavior adequately. It is thin on authentication/permission expectations and error behavior, which matter for a 'current user' lookup, but nothing critical is missing 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?

Schema description coverage is 100%, so both the 'fields' filter and 'site_id' are already documented with enums. The description's note that all fields are returned by default and a filtered subset is optional mirrors the schema wording rather than adding new meaning, so baseline 3 applies.

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 a specific verb and resource: returns profile details for the *current authenticated* user, which implicitly distinguishes it from sibling tools like wp_get_user or emcp-tools-get-user that take a user identifier. It does not name those siblings directly, so no explicit differentiation, but an agent can infer the scope from 'current authenticated 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?

Usage is only implied through motivation phrases ('support personalization, auditing, and access-aware behavior'). There is no explicit statement of when to prefer this over the many sibling user/profile tools, nor any when-not condition or prerequisite (e.g., what happens when no user is authenticated).

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