ban_participant

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

No annotations provided, so description must cover behavior. It explains ban equals kick plus cannot rejoin, and the effect of 'until' and 'unban'. Missing details like required admin permissions or whether operation is reversible.

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?

Extremely concise: two lines of Chinese defining the action followed by compact parameter documentation. No redundant sentences. Front-loaded with the verb and object.

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?

Tool complexity is low; description covers primary behavior and parameters. Output schema exists (not shown) so return values are unneeded. Minor omissions: no mention of error conditions or permission requirements.

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 coverage is 0%, but description compensates by explaining all 4 parameters: 'chat' as group/channel, 'user' as target user, 'until' with format example, and 'unban' as removal of ban. Adds meaning beyond bare schema names.

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?

Description clearly states the tool bans/unbans group members (ban = kick and cannot rejoin). Distinguishes from sibling 'kick_participant' which likely only kicks without permanent ban.

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?

Provides parameter usage details for 'until' (e.g., '+7d' for time-limited ban) and 'unban' flag. Implicitly differentiates from kick by specifying ban is permanent unless unban is set, but no explicit when-to-use guidance.

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