unban_participant

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the operation is known to be a non-read write action. However, the description adds no additional behavioral context, such as whether unbanning allows the user to rejoin, whether it fails if the user isn't banned, or any permission requirements. It offers nothing beyond the tautological 'unban'.

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, concise sentence with no wasted words. It is front-loaded with the action and object. However, it is so short that it borders on under-specification, but for conciseness alone it earns a high score because there is no redundancy or irrelevant detail.

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?

The tool exists within a rich set of moderation sibling tools (ban_participant, kick_participant, restrict_participant), yet the description does not relate to them or explain the context of use. There is no mention of reversibility, effect on user access, or any edge cases. While the output schema exists, the description remains incomplete for an agent to understand the full behavioral scope.

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 description does not mention the parameters at all. It does not clarify that 'chat' and 'user' are identifiers (chat ID and user ID), nor does it explain how to represent them (integer vs string). With no compensation from the description, the agent has no semantic guidance for the two required parameters.

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 'Снять бан с участника' clearly states the action (remove/unban) and the exact resource (a participant's ban). It unambiguously distinguishes this from sibling tools like ban_participant or kick_participant, and even from unblock_user, because it specifies 'бан' (ban) in a participant context.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this is the inverse of ban_participant, nor does it specify prerequisites like admin permissions or that the user must currently be banned. There is no explicit context or exclusion, leaving the agent to infer usage from the name.

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