user_public_by_id_post

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

With no annotations, the description carries the full burden but only restates the operation. It does not mention that this is a non-idempotent write (POST) requiring confirm:true in rw mode, nor any auth, rate-limit, or side-effect behavior — all of which are vital for an agent deciding whether to invoke a mutating endpoint.

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 mixes a raw route string, Russian sentence, and metadata labels ('Тег: Шаблоны', 'Спека: user') that duplicate machine-readable context. It is not front-loaded around what the tool does, and the extraneous lines dilute the signal.

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 4-parameter mutating tool with a nested body object, no annotations, and no output schema, the description should explain the confirm/preview flow and the admin impersonation semantics. It leaves a critical behavioral gap around confirm:true in rw mode entirely to 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 description coverage is 100%, so the schema already documents id, body, confirm, and user_id thoroughly. The description adds nothing beyond the generic phrase 'с аргументами' (with arguments), so baseline 3 applies.

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 'Выполнить публичный шаблон с аргументами' (execute a public template with arguments), which conveys a specific verb and resource, but the accompanying raw HTTP line and Russian metadata tags (Тег, Спека) are noise rather than clarification. It is unclear how this POST differs from the sibling GET user_public_by_id_get beyond the HTTP method.

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 guidance is given. The description does not explain when to POST a public template versus GETting one, nor when to prefer user_template_by_id_post. The only usage hint ('confirm') lives in the schema, not the description.

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