telegram-set-profile-photo

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

The description adds behavioral context beyond annotations: it specifies supported image/video formats, file size limits (square, up to 10s for video), and the fallback feature. It aligns with annotations (readOnlyHint=false, write operation). Missing details on side effects like overwriting or rate limits.

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 sentences, front-loaded with the primary action, and no unnecessary details. Every sentence adds value.

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 no output schema, the description does not explain the return value or confirmation of success. For a mutation tool with 4 parameters, it covers usage well but leaves out post-action behavior.

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 baseline is 3. The description adds extra context about file formats and fallback but does not significantly enhance understanding of parameters beyond their schema descriptions.

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 'Upload and set a new profile photo from a local file' and specifies supported formats (JPEG/PNG, MP4). It distinguishes from sibling tools like telegram-get-profile-photo and telegram-delete-profile-photo by focusing on setting a new 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?

Provides context on file types and the fallback option, but does not explicitly state when to use this tool versus alternatives (e.g., send-file). It mentions that URLs are rejected, which is a helpful guideline for input format.

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