Edit Chat

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

No annotations are provided, so the description carries full burden. It states the admin requirement but does not disclose potential side effects, whether changes are reversible, or error handling (e.g., what happens if not admin). Minimal behavioral context beyond the basic 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?

The description is two sentences, front-loading the key actions and then stating the admin requirement. Every word is necessary, no redundancy.

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?

No output schema exists. The description covers the purpose and a critical requirement, but fails to mention idempotency, notification behavior (though schema has notify_members), or error conditions. For a mutation tool with 5 parameters, it is somewhat incomplete.

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 coverage is 100%, so the description does not need to add parameter details. The description lists the actions (rename, change description, update icon) which maps to params title, description, icon, but adds no additional meaning or nuance beyond the schema.

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 tool's actions: rename a chat, change description, or update icon. It uses a specific verb ('edit') and resource ('chat'), and distinguishes from siblings like edit_message by focusing on chat-level properties.

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 mentions a prerequisite (bot must be admin), which helps in usage. However, it does not provide guidance on when to use this tool vs alternatives like get_chat or delete_message, nor when not to use it.

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