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 possible side effects (openWorldHint=true). The description accurately states it uploads and sets a new profile photo, implying replacement of the current one. It adds context about file types and fallback, which goes beyond the annotations.

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 main action, followed by optional details. No redundant information, 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?

The description covers the main purpose and important options. It could mention that the photo replaces the current one or describe the return value, but given no output schema, the description is largely complete for a straightforward upload action.

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 input schema has 100% coverage with descriptions. The description adds value by specifying file formats (square, up to 10s for MP4) and clarifying the fallback setting. This provides meaning beyond what is in 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 uses specific verbs 'Upload and set' and identifies the resource as 'profile photo'. It clearly distinguishes from siblings like 'telegram-delete-profile-photo' and 'telegram-get-profile-photo' by specifying the action of 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?

The description provides format constraints (JPEG/PNG/MP4) and optional fallback, implying when to use it. However, it does not explicitly state when not to use it or compare to alternatives like 'telegram-update-profile' which may also affect profile photo.

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