tg_chat_edit

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

The annotations already provide readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the description does not need to restate those. It adds useful behavioral details such as 'slowmode: seconds between messages per member, 0 turns it off (supergroups only)' and 'forum: true turns the supergroup into a forum with topics.' However, it does not disclose side effects such as overwriting existing values or the potential consequences of changing default member 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?

One concise introductory sentence followed by a compact Args block. Every line adds either a parameter definition or a constraint, and there is no filler or repetition of schema information.

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 7-parameter tool with nested objects and no output schema, the description covers the parameter semantics thoroughly and includes important constraints. It is slightly incomplete regarding how the chat identifier should be provided and what destructive consequences may follow, but the core calling contract is well specified.

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%, so the description must carry the full burden for parameter meaning, and it does. It explains chat, title, about, photo, slowmode, permissions (with example JSON and allowed keys), and forum, giving each parameter far more meaning than the 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?

The description names the verb 'Change' and the exact resource ('a group's or channel's'), then enumerates the affected attributes: 'title, description, photo, slow mode, the default rights of its members, or turn topics (forum mode) on and off.' This clearly scopes the tool to chat-level settings, though it does not explicitly differentiate it from siblings like tg_topic_edit or tg_edit.

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?

There is no explicit guidance about when to use tg_chat_edit versus alternatives. The only contextual note is 'supergroups only' for slowmode, which helps slightly but does not explain when this tool should be preferred over sibling tools such as tg_topic_edit, tg_moderate, or tg_edit.

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