telegram-set-profile-photo

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

Annotations indicate a write operation (readOnlyHint false) and open world (openWorldHint true). The description adds behavioral details: supports static and animated avatars, square constraint, 10-second limit, and fallback option. It does not mention that it replaces the current photo, but the context is clear.

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?

Two concise sentences, front-loaded with the primary action. Every sentence adds essential information without 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?

Given the simple write nature and lack of output schema, the description covers file types, constraints, and the fallback option. It does not mention immediate effect or replacement, but these are implied.

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?

All parameters are described in the schema (100% coverage). The description adds value by specifying file type constraints (JPEG/PNG/MP4), square requirement, and video duration limit beyond the schema's 'absolute local filesystem path'.

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 uses a specific verb ('Upload and set') and resource ('profile photo'), lists supported formats (JPEG/PNG/MP4), and mentions optional fallback. It clearly differentiates from siblings like telegram-delete-profile-photo.

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 clearly states the tool's purpose (upload and set profile photo) and conditions (from local file, specific formats). It implicitly indicates when to use it (to set a new photo) but does not explicitly compare with alternatives like telegram-update-profile or telegram-delete-profile-photo.

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