edit_chat_photo

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

Annotations indicate a non-read-only, non-idempotent, non-destructive mutation, but the description adds no behavioral context. It does not disclose that the avatar is replaced, whether admin permissions are required, or how the file is accessed (local path vs upload). This is a significant gap for a mutating 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 a single, concise sentence with zero filler. It states the core purpose directly, which is appropriately sized for a simple tool.

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?

Given the operation is a mutation with no behavioral or usage context, the description is incomplete. It does not explain return values (though output schema exists, the description is still lacking prerequisites and edge cases) or usage scenarios. For a tool of this simplicity, more context is needed to avoid misuse.

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 compensate. It implicitly maps 'chat/channel' to the 'chat' parameter and 'file' to 'file_path', but does not clarify accepted formats (peer identifiers, path types) or any constraints. Minimal added value over the bare 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 action: 'Set the chat/channel avatar from a file.' It specifies the verb (set), the resource (avatar), and the target (chat/channel), distinguishing it from title/about edits and file sending. Slight lack of differentiation from sibling tools, but scope is clear.

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?

No guidance on when to use this tool versus alternatives like send_file or edit_chat_title. The description does not mention prerequisites (e.g., admin rights) or exclusions, leaving the agent to infer usage.

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