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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description needn't re-litigate safety. It adds the underlying endpoint (POST /v1/rex/UserProfile/read) and the field set, but says nothing about what happens if no account is signed in, auth failure modes, or whether the response is cached.

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?

Three short fragments, front-loaded with the identity/scope and followed by the returned fields, then the usage cue and endpoint. No filler or restatement of the title beyond what adds meaning.

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?

With no output schema, the description carries the burden of describing the return payload and does so by enumerating the six fields. It's nearly complete for a zero-param read; minor gaps are behavioral edge cases (unauthenticated state, error responses) that an agent might still want.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies no input is needed by framing this as an identity lookup.

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 resource (the signed-in Rex user) and enumerates exactly what it returns: user id, name, email, ownership flag, position and default office. This cleanly separates it from the sibling rex_search_users, which searches arbitrary users rather than resolving the current identity.

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?

"Good first call" gives concrete, actionable sequencing guidance — an agent knows to invoke this during bootstrap before user-scoped calls. It stops short of explicit exclusions (e.g., 'use rex_search_users to look up other users'), so it earns a 4 rather than a 5.

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