setChatDescription

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the key traits: it is a mutating operation, it requires specific admin permissions, and it returns True on success — all useful beyond the schema. It does not disclose failure/error behavior, partial effects, or that an empty description clears the field, which are moderate gaps for a write operation.

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 with no filler: the first front-loads the action and target resource, the second packs the permission prerequisite and return value. Every sentence earns its place, and the whole description is appropriately sized for the tool's simplicity.

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 simple two-parameter mutation with a fully documented schema, this description covers what the tool does, the permission condition under which it works, and its return value — important since there is no output schema. The main omission is error-behavior detail (e.g., what happens when the bot lacks rights), which is relatively minor given the low complexity and complete parameter documentation.

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 both chat_id and description are already fully documented with types, formats, and constraints (e.g., '0-255 characters'). The tool description adds no parameter-level detail, but at this coverage level the schema carries the load and the 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 a specific verb ('Change') and resource ('description of a group, a supergroup or a channel'), making the operation unambiguous. The explicit chat-type scope distinguishes it from sibling tools like setMyDescription (bot's own description) and setChatTitle (title rather than description), so an agent can select it correctly without opening the schema.

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 a clear prerequisite — the bot must be an administrator with can_change_info rights — which tells an agent when the call will succeed. However, it gives no explicit guidance on when to prefer this tool over alternatives such as setChatTitle or setChatPhoto, nor does it mention when not to use it. The usage context is implied rather than fully routed.

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