user_password_auth_get

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no auth/permission requirements, no indication of what 'status' means, and no note about the user_id impersonation behavior. The GET verb weakly implies a read, but that is the schema/route convention, not description content.

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?

It is short and front-loads the route, which is good, but 'Тег: Пользователи' and 'Спека: user' are template metadata that add no decision value for an agent. Compact but partly noise.

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 tool with three parameters, no annotations, and no output schema, the description should say what the status read returns and how user_id impersonation affects it. Instead it supplies only the endpoint and a title, leaving key call semantics undocumented.

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% (limit, offset, user_id all documented, including 'admin acts on behalf of this user'), so the schema does the heavy lifting. The description adds no parameter meaning of its own, making the baseline 3 correct.

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 the HTTP route (GET /user/password-auth) and a Russian gloss meaning 'password login status', which gives a rough verb+resource. However, it is a bare endpoint label with no differentiation from the many neighboring auth tools, and the purpose is only inferable for a non-Russian-reading agent.

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?

There is no guidance on when to call this versus siblings such as user_password_auth_post, user_password_auth_delete, user_auth_post, or user_passwd_post. The agent is left to guess that this is the read variant of a password-auth group.

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