get_user

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

The readOnlyHint=true annotation already declares the safety profile, so the bar is lower, but the description adds nothing behavioral beyond the purpose line: no permissions/scope requirements, no not-found behavior, no rate-limit or scoping notes. The one extra fact (login OR UID) is really parameter semantics, not 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?

A single front-loaded sentence with zero filler, correctly leading with the action and resource. It is terse to the point of omitting useful qualifiers, but nothing in it is wasted.

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?

An output schema exists, so return values need not be described, and the tool is a simple single-parameter read. However, the description is written in Russian while the tool surface, schema, and sibling names are English, and it omits any scoping or failure-mode context, leaving it only minimally adequate.

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 0% and the sole parameter "user_id" is titled only "User Id", so the description must compensate. It does partially, by disclosing that the value may be either a login or a UID, which is genuinely beyond the schema — but it gives no format, case-sensitivity, or ambiguity-resolution guidance.

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 ("Получить пользователя организации" = get an organization user) plus the lookup keys (login or UID). This is enough to distinguish it from get_current_user (self) and list_users/search_users, though it does not name those siblings explicitly.

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?

No when-to-use, when-not-to-use, or alternative routing is given. An agent cannot tell from the description whether to reach for this, search_users, or list_users when it only has partial identity information; the choice is left to inference from the parameter.

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