promote_chat_member

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

Annotations already indicate a mutating (readOnlyHint=false), idempotent, and non-destructive operation. The description adds that it applies to supergroups/channels and involves promotion/demotion, but doesn't disclose important behaviors such as how omitted permission flags are interpreted (likely all false) or the need for admin rights.

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 that directly conveys the core function with no wasted words. It is well-structured and easily parsed.

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 19 parameters and no output schema, this one-line description is severely incomplete. It doesn't explain how permission flags map to promotion/demotion, what happens when no flags are set, or any operational prerequisites, leaving an agent with insufficient context to use it correctly.

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?

With 19 parameters and only 11% schema description coverage, the description must compensate, but it mentions no parameters at all. The many boolean permission flags are left completely unexplained, making it impossible to understand their effect from the description.

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 ('Promote or demote'), the target ('a user'), and the scope ('in a supergroup or channel'). This distinguishes it from sibling tools like ban_chat_member or restrict_chat_member and is not a tautology.

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 guidance is provided on when to use this tool versus alternatives. While the name implies promotion/demotion, the description does not mention when to prefer it over restrict_chat_member or set_chat_administrator_custom_title, nor any prerequisites like being an administrator.

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