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

readOnlyHint=true already declares the safe-read profile, and the description adds genuine value by enumerating the returned fields despite there being no output schema, plus the underlying endpoint. It does not explain what happens when the user is not found or the effect of include_suspended.

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?

One front-loaded sentence naming the resource, key modes and payload, plus a short endpoint reference. No wasted words.

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 read tool with annotations covering safety and no output schema, listing the returned fields is exactly the compensating detail needed. Only the suspended-user behavior is left unaddressed, and that is covered by the schema.

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 coverage is 100%, so baseline is 3. The description reinforces that 'user' accepts either an id or an email, but says nothing about include_suspended, adding little beyond the schema.

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?

Specific verb (Fetch) + resource (one user) + identifier modes (id or email), and it enumerates the returned payload (profile, role, tags, sign-up fields, UTMs, last login). This clearly distinguishes it from learnworlds_list_users and learnworlds_get_user_course_progress.

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?

Implies single-user lookup keyed by id or email, which is enough context to pick it over list_users, but it never states when to prefer it over siblings like get_user_course_progress or when-not (e.g., bulk lookups). No explicit alternatives are named.

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