promote_chat_member

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

No annotations provided. The description does not disclose behavioral traits such as required permissions, side effects (e.g., overwriting existing admin rights), or whether promotion is reversible. Lacks important context beyond the action itself.

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?

Two sentences, no redundant information. The first sentence states the core purpose, and the second adds a useful nuance about optional chat_id. Efficient and clear.

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 complex tool with 14 parameters and no output schema, the description lacks details on what happens after promotion (e.g., return value, success/failure conditions). It is insufficient for an agent to fully understand the tool's behavior.

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 covers all 14 parameters with descriptions (100% coverage). The description adds value by explaining the default chat_id behavior. While most parameters are self-explanatory in schema, the extra context on chat_id is helpful.

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 'Promote a user to admin in a chat' using a specific verb and resource. It distinguishes from sibling tools like ban_chat_member or restrict_chat_member by focusing on admin promotion.

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 context about default chat when chat_id is omitted, but does not explicitly state when to use this tool versus alternatives like set_chat_administrator_custom_title. Lacks when-not guidance.

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