chats_update

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation risk is structured. The description adds one genuinely useful fact — that the change 'reaches other people on the platform' — but the 'deletes, or redirects data' clause is generic boilerplate that does not describe what this rename actually affects or whether it needs elevated permissions.

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 purpose is front-loaded in three words and the endpoint metadata line is compact. However, the middle warning sentence is boilerplate that is largely inapplicable to a rename and dilutes the useful content.

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?

With annotations covering the safety profile and no output schema to explain, the main remaining burden is parameter meaning and usage context — both of which are thin. An agent would still need to infer who can rename, whether it applies to group chats, and what the required IDs reference.

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% and the description only implies the 'name' parameter via the word 'Rename'. It says nothing about the required chatId and channelId, that 'name' is optional, or the accepted value format, leaving two required identifiers undocumented.

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 opening 'Rename a chat' gives a specific verb and resource, which cleanly separates this tool from chats_create, chats_delete, and chats_get in the sibling list. It does not, however, explicitly contrast itself with any alternative or state the scope of the rename (e.g., group vs direct chat).

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 guidance on when to choose this over sibling update tools (contacts_update, messages_update, channels_update) or what preconditions apply. The 'get the user's confirmation first' line is a generic safety instruction rather than tool-selection guidance.

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