Get user

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds that the data is 'public profile information,' which is useful, but it does not disclose error cases, authentication needs, or return behavior. This is acceptable for a simple getter but is not rich beyond the annotations.

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, front-loaded sentence with no filler or repetition. Every word contributes to understanding what the tool does.

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 single-parameter getter with a readOnlyHint and no output schema, the description is mostly complete: it identifies the resource, the target user, and the public nature of the data. It could be slightly stronger by explicitly pointing to get_current_user, but nothing critical is missing.

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 schema already documents the single parameter as 'User ID or username' with 100% coverage. The description's phrase 'specific user' reinforces the parameter's purpose but adds no new semantic detail beyond what the schema provides.

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 clear verb and resource: it retrieves public profile information for a specific user. It is distinguishable from tribeunal_get_current_user through the phrase 'specific user,' though it does not explicitly name that sibling or contrast with it.

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?

The description makes it clear this tool is for looking up a particular user's public profile by ID or username, which gives an agent useful context. It does not explicitly state when not to use it or mention get_current_user as the alternative, but the intended use is inferable and clear.

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