set_chat_photo

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

The description lacks behavioral detail. It does not disclose error handling (e.g., invalid path, permission issues), side effects, or any constraints. With no annotations, the description fails to provide safety or usage context.

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 very concise (one sentence), which is efficient but potentially too brief. It could include more detail without becoming verbose.

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 mutation nature and lack of annotations, the description is incomplete. It does not cover prerequisites (e.g., admin rights), potential errors, or return value, despite an output schema existing.

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?

The description adds meaning beyond the schema by indicating 'local image' for the path parameter and 'group/channel avatar' for the chat parameter. However, it does not clarify types (e.g., chat can be username or ID) or path format.

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 and resource: 'set local image as group/channel avatar.' It differentiates from sibling tools like set_profile_photo and set_chat_title, though it could be more explicit about the target being a group or channel.

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 is provided on when to use this tool vs alternatives (e.g., set_profile_photo). There is no mention of prerequisites, permissions, or scenarios where this tool is appropriate.

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